From: Andrew Morton <akpm@osdl.org>
To: busterbcook@yahoo.com, linux-kernel@vger.kernel.org,
Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: pdflush eating a lot of CPU on heavy NFS I/O
Date: Wed, 28 Apr 2004 22:29:50 -0700 [thread overview]
Message-ID: <20040428222950.6406a9f0.akpm@osdl.org> (raw)
In-Reply-To: <20040428214741.7d5b3ae1.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
>
> Now, that redirtying of the inode _should_ have moved the inode off the
> s_io list and onto the s_dirty list. But for some reason it looks like it
> didn't, so we get stuck in a loop. I need to think about it a bit more.
OK, it looks like nfs_writepages() might have been encountered the
congested flag and it baled out without doing anything - the inode is still
on the temporary s_io list, and no pages were redirtied, hence the inode
wasn't redirtied, hence it remains stuck on the s_io list. The patch I
sent will fix that up.
next prev parent reply other threads:[~2004-04-29 5:30 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-28 5:18 Brent Cook
2004-04-28 6:02 ` Andrew Morton
2004-04-28 7:29 ` Phy Prabab
2004-04-28 10:18 ` Sven Geggus
2004-04-28 13:50 ` Brent Cook
2004-04-28 19:48 ` Andrew Morton
2004-04-28 20:12 ` Brent Cook
2004-04-28 20:39 ` Brent Cook
2004-04-28 21:19 ` Trond Myklebust
2004-04-29 3:55 ` Brent Cook
2004-04-29 4:21 ` Trond Myklebust
2004-04-29 4:42 ` Andrew Morton
2004-04-29 1:24 ` Andrew Morton
2004-04-29 3:53 ` Brent Cook
2004-04-29 4:02 ` Andrew Morton
2004-04-29 4:03 ` Andrew Morton
2004-04-29 4:37 ` Brent Cook
2004-04-29 4:47 ` Andrew Morton
2004-04-29 5:29 ` Andrew Morton [this message]
2004-04-29 13:19 ` Brent Cook
2004-04-29 3:54 ` Andrew Morton
2004-04-28 6:06 ` Brett E.
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=20040428222950.6406a9f0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=busterbcook@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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®