From: Florin Iucha <florin@iucha.net>
To: Fengguang Wu <wfg@mail.ustc.edu.cn>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
Date: Tue, 30 Oct 2007 22:52:45 -0500 [thread overview]
Message-ID: <20071031035245.GQ25561@iucha.net> (raw)
In-Reply-To: <20071031000242.GP25561@iucha.net>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
On Tue, Oct 30, 2007 at 07:02:42PM -0500, Florin Iucha wrote:
> I have added the patches and started a linux kernel compilation, and
> something really interesting happens. I run the build with the
> equivalent of "make -j3" and in a separate console I am watching the
> build with 'top'. The build consumes 98% of both CPUs. If I stop the
> output in the build console with "Ctrl-S", one core goes to idle,
> while the other is in 50% waiting, then goes to 75% waiting. When I
> resume the build with "Ctrl-Q", the build starts to use both CPUs at
> 98-99%. The NFS4 use was minimal, as I did not login with Gnome, but
> just logged on the console. Also, the CPU that is in 75% waiting
> state changes occasionally. 'Top' shows pdflush in D state, using
> 5-6% of CPU.
I forgot the traces:
http://iucha.net/2.6.24-rc1/fw.1.gz
http://iucha.net/2.6.24-rc1/fw.2.gz
http://iucha.net/2.6.24-rc1/fw.3.gz
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-10-31 3:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 15:24 pdflush stuck in D state with v2.6.24-rc1-192-gef49c32 Florin Iucha
2007-10-29 13:46 ` Trond Myklebust
2007-10-29 15:01 ` Florin Iucha
2007-10-29 18:43 ` Trond Myklebust
2007-10-29 18:48 ` Florin Iucha
[not found] ` <E1ImlvH-0003YH-Qf@localhost>
2007-10-30 7:54 ` Fengguang Wu
2007-10-30 11:42 ` Florin Iucha
[not found] ` <E1ImpbK-0000l3-1u@localhost>
2007-10-30 11:49 ` Fengguang Wu
2007-10-30 11:55 ` Florin Iucha
2007-10-31 0:02 ` Florin Iucha
2007-10-31 3:52 ` Florin Iucha [this message]
[not found] ` <E1In7S9-0001rv-NO@localhost>
2007-10-31 6:53 ` Fengguang Wu
2007-10-31 12:16 ` Florin Iucha
2007-10-31 17:53 ` Florin Iucha
[not found] ` <E1InUH6-0001vE-1Y@localhost>
2007-11-01 7:15 ` Fengguang Wu
2007-11-01 12:25 ` Florin Iucha
[not found] ` <E1InZht-0004lr-NN@localhost>
2007-11-01 13:03 ` Fengguang Wu
2007-11-01 14:14 ` Florin Iucha
[not found] ` <E1InlPV-0001f1-SL@localhost>
2007-11-02 1:33 ` Fengguang Wu
2007-11-02 2:10 ` Florin Iucha
[not found] ` <E1Inw51-0001e8-PS@localhost>
2007-11-02 12:56 ` Fengguang Wu
2007-11-02 13:32 ` Florin Iucha
2007-11-11 13:43 ` Thomas
2007-12-04 10:28 ` [Bug 9291] " Ingo Molnar
2007-12-04 17:45 ` Thomas Kuther
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=20071031035245.GQ25561@iucha.net \
--to=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=trond.myklebust@fys.uio.no \
--cc=wfg@mail.ustc.edu.cn \
/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