mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bret Towe" <magnade@gmail.com>
To: "Nikita Danilov" <nikita@clusterfs.com>
Cc: "Ananiev, Leonid I" <leonid.i.ananiev@intel.com>,
	"Linux Kernel Mailing List" <Linux-Kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: moving dirty pages balancing to pdfludh entirely
Date: Wed, 5 Jul 2006 10:19:16 -0700	[thread overview]
Message-ID: <dda83e780607051019q4bcdf4e2w346634441cba492@mail.gmail.com> (raw)
In-Reply-To: <17579.37504.509233.959683@gargle.gargle.HOWL>

On 7/5/06, Nikita Danilov <nikita@clusterfs.com> wrote:
> Bret Towe writes:
>
> [...]
>
>  >
>  > are you sure about that? cause that sounded alot like an issue
>  > i saw with slow usb devices (mainly a usb hd on a usb 1.1 connection)
>  > the usb device would fill up with write queue and local io to say /dev/hda
>  > would basicly stop and the system would be rather useless till the usb
>  > hd would finish writing out what it was doing
>  > usally would take several hundred megs of data to get it to do it
>
> There may be bazillion other reasons for slow device making system
> unresponsive in various ways. More details are needed (possibly in
> separate thread).

well at this time all i know is one will be writing to the usb hd its queue
will fill up and if say some gtk app wants to write to disk it will freeze
until the usb hd is completely done
i will look into it at some point when i have time and get more info on
it and post a proper report on the issue unless its already been fixed

>  >
>  > ive not tried it in ages so maybe its been fixed since ive last tried it
>  > dont recall the kernel version at the time but it wasnt more than a
>  > year ago
>  >
>
> Nikita.
>

  reply	other threads:[~2006-07-05 17:19 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04 19:12 Ananiev, Leonid I
2006-07-04 20:20 ` Nikita Danilov
2006-07-04 22:24   ` Bret Towe
2006-07-05 10:20     ` Nikita Danilov
2006-07-05 17:19       ` Bret Towe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-06 21:07 Ananiev, Leonid I
2006-07-06 16:33 Ananiev, Leonid I
2006-07-06 17:37 ` Nikita Danilov
2006-07-06 13:54 Ananiev, Leonid I
2006-07-06 15:16 ` Nikita Danilov
2006-07-06 11:47 Ananiev, Leonid I
2006-07-06  4:30 Ananiev, Leonid I
2006-07-06  6:34 ` Nikita Danilov
2006-07-05 19:50 Ananiev, Leonid I
2006-07-05 20:05 ` Nikita Danilov
2006-07-05 19:28 Ananiev, Leonid I
2006-07-05 20:14 ` Nikita Danilov
2006-07-05 18:10 Ananiev, Leonid I
2006-07-05 19:07 ` Nikita Danilov
2006-07-05 15:48 Ananiev, Leonid I
2006-07-05 14:28 Ananiev, Leonid I
2006-07-05 14:57 ` Nikita Danilov
2006-07-05  5:40 Ananiev, Leonid I
2006-07-05 10:17 ` Nikita Danilov
     [not found] <B41635854730A14CA71C92B36EC22AAC0541F6@mssmsx411>
2006-07-04 13:12 ` Nikita Danilov
2006-07-04 13:07 Ananiev, Leonid I
2006-07-04 11:43 Ananiev, Leonid I
2006-07-04 11:56 ` Nikita Danilov
2006-07-04  9:55 Nikita Danilov
2006-07-04  9:44 Ananiev, Leonid I
2006-07-04  8:35 Ananiev, Leonid I
2006-07-03 16:43 Ananiev, Leonid I
2006-07-04  8:32 ` Nikita Danilov
2006-06-27  5:31 Ananiev, Leonid I
2006-06-28 11:33 ` Nikita Danilov
2006-07-03 17:31   ` Antonio Vargas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dda83e780607051019q4bcdf4e2w346634441cba492@mail.gmail.com \
    --to=magnade@gmail.com \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=leonid.i.ananiev@intel.com \
    --cc=nikita@clusterfs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®