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: Tue, 01 May 2007 10:40:03 +0200 [thread overview]
Message-ID: <4636FCE3.6000405@gmail.com> (raw)
In-Reply-To: <20070430114449.1dad1ab2.akpm@linux-foundation.org>
Andrew Morton napsal(a):
> I would check the anticipatory scheduler as well, please. I don't know
> what no-op would do with a workload like that, but it probably isn't very
> good.
>
> You appear to believe that it's related to the CPU scheduler?
Oh, no. I have really no idea, what may cause this :).
> That's a bit
> unexpected - it sounds more like a VFS/IO thing? But stranger things have
> happened.
I think so.
> I guess it's time to end the staircase experiment in -mm.
> http://userweb.kernel.org/~akpm/js.bz2 is my current rollup (against
> 2.6.21) minus staircase and related things. Pretty please.
Anticipatory + -js is no change. Going to try vanilla and in both cases whether
it works or not, I'll bisect either -mm or vanilla.
regards,
--
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-05-01 8:40 UTC|newest]
Thread overview: 14+ 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
2007-04-30 18:44 ` Andrew Morton
2007-05-01 8:40 ` Jiri Slaby [this message]
2007-05-01 10:06 ` Jiri Slaby
2007-05-04 14:58 ` Jiri Slaby
2007-05-04 14:58 ` Jiri Slaby
2007-05-04 15:02 ` 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=4636FCE3.6000405@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.