From: Florin Iucha <florin@iucha.net>
To: Fengguang Wu <wfg@mail.ustc.edu.cn>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: pdflush stuck in D state with v2.6.24-rc1-192-gef49c32
Date: Fri, 2 Nov 2007 08:32:39 -0500 [thread overview]
Message-ID: <20071102133239.GI25561@iucha.net> (raw)
In-Reply-To: <E1Inw51-0001e8-PS@localhost>
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
On Fri, Nov 02, 2007 at 08:56:55PM +0800, Fengguang Wu wrote:
> > > ---
> > > fs/reiserfs/stree.c | 3 ---
> > > 1 file changed, 3 deletions(-)
> > >
> > > --- linux-2.6.24-git17.orig/fs/reiserfs/stree.c
> > > +++ linux-2.6.24-git17/fs/reiserfs/stree.c
> > > @@ -1458,9 +1458,6 @@ static void unmap_buffers(struct page *p
> > > }
> > > bh = next;
> > > } while (bh != head);
> > > - if (PAGE_SIZE == bh->b_size) {
> > > - cancel_dirty_page(page, PAGE_CACHE_SIZE);
> > > - }
> > > }
> > > }
> > > }
> >
> > ... and with the above patch applied.
> >
> > Copying 300 MB from root (ext3) to the new file system did not trigger
> > the pdflush condition. But then I did a
> > cd $MOUNTPOINT && find . -exec md5sum {} \;
> > and that brought one cpu to 75% iowait.
>
> Immediately? Do you have the debug printk messages this time(with the
> above patch)?
No, but I will add them this afternoon.
> > I have attached my .config, if it helps.
>
> It's really curious - I tried your .config and commands, and still
> could not trigger the high iowait. I'm running 64bit Intel Core 2,
> and kernel 2.6.24-rc1-git6 with the above patch.
Curious but 100% reproducible, at least on my box. What I'm going to
try is booting into the kernel with your patch and just doing the find
/ md5sum. It would be really interesting if the read-only access
triggers it.
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-11-02 13:32 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
[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 [this message]
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=20071102133239.GI25561@iucha.net \
--to=florin@iucha.net \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--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