From: "Jiri Slaby" <jirislaby@gmail.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.21-mm1: many processes end up in D state
Date: Mon, 30 Apr 2007 20:14:05 +0200 [thread overview]
Message-ID: <4af2d03a0704301114sc84b358td8781c91b8564c38@mail.gmail.com> (raw)
In-Reply-To: <20070430110510.1f559d34.akpm@linux-foundation.org>
On 4/30/07, Andrew Morton <akpm@linux-foundation.org> wrote:
> On Mon, 30 Apr 2007 17:39:19 +0200
> Jiri Slaby <jirislaby@gmail.com> wrote:
>
> > Hi,
> >
> > I have a problem with higher disk loads (e.g. running git-log or yum update).
> > Many processes end up in D state and system is unusable -- I'm not able to run
> > anything but smooth mouse moving when this happens.
> >
> > If I wait for a 20-30sec it becomes usable. This happens in 2.6.21-rc7-mm2 and
> > also in 2007-04-28-05-06 broken-out snapshot. I think 2.6.21-rc6-mm1 worked
> > fine, but I'm uncertain. If it is important, let me know to re-test.
> >
>
> It is important, but I doubt if retesting 2.6.21-rc6-mm1 will clarify
> things a lot.
>
> Could you try switching to a different IO scheduler please? Anticipatory
> would suit.
As I wrote below the sysrq-t, switch to noop didn't help, but it seems
that it's harder to reproduce with that:
<cite it's_bad_to_write_anything_below_logs="true">
Note that yum works on lvm on raid0 and git too, but on the another md volume.
Both ext3s. Drivers are sata_promise and ata_piix (sata disk); CFQ scheduler.
Using noop is no change (but seems to be harder to reproduce with it). I figured
out that it probably happens when 2+ processes are on both "processors" (HT on
P4) and are IO wait (multiload-applet shows red above the half).
Swap usage is 0 all the time.
</cite>
> Please keep a close eye on mainline, too. Wait for it to appear there :(
Ok, I'll try to play with that...
thanks,
--
http://www.fi.muni.cz/~xslaby/ Jiri Slaby
faculty of informatics, masaryk university, brno, cz
e-mail: jirislaby gmail com, gpg pubkey fingerprint:
B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E
next prev parent reply other threads:[~2007-04-30 18:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-30 15:39 2.6.21-mm1: many processes end up in D state Jiri Slaby
2007-04-30 18:05 ` Andrew Morton
2007-04-30 18:14 ` Jiri Slaby [this message]
2007-04-30 18:44 ` Andrew Morton
2007-05-01 8:40 ` Jiri Slaby
2007-05-01 10:06 ` Jiri Slaby
2007-05-04 14:58 ` Jiri Slaby
2007-05-04 15:02 ` Jiri Slaby
-- strict thread matches above, loose matches on Subject: below --
2007-05-04 19:19 Mikael Pettersson
2007-05-05 15:30 ` Tejun Heo
2007-05-05 23:46 Mikael Pettersson
2007-05-07 9:52 ` Jiri Slaby
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=4af2d03a0704301114sc84b358td8781c91b8564c38@mail.gmail.com \
--to=jirislaby@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
/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