From: Phy Prabab <phyprabab@yahoo.com>
To: Andrew Morton <akpm@osdl.org>, busterbcook@yahoo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: pdflush eating a lot of CPU on heavy NFS I/O
Date: Wed, 28 Apr 2004 00:29:18 -0700 (PDT) [thread overview]
Message-ID: <20040428072918.56419.qmail@web90007.mail.scd.yahoo.com> (raw)
In-Reply-To: <20040427230203.1e4693ac.akpm@osdl.org>
If you guys could please either cc or keep this on the
mailing list I would greatly appreciate it. I am
currently planning to deploy a dual Xeon FS with
2.6.5+akpm-mm6 and would like to know what the issue
is that Brent is seeing.
Thanks!
--- Andrew Morton <akpm@osdl.org> wrote:
> Brent Cook <busterbcook@yahoo.com> wrote:
> >
> > Running any kernel from the 2.6.6-rc* series
> (and a few previous
> > -mm*'s),
>
> It's a shame this wasn't reported earlier.
>
> > the pdflush process starts using near 100% CPU
> indefinitely after
> > a few minutes of initial NFS traffic, as far as I
> can tell.
>
> Please confirm that the problem is observed on the
> NFS client and not the
> NFS server? I'll assume the client.
>
> What other filesystems are in use on the client?
>
> Please describe the NFS mount options and the number
> of CPUs and the amount
> of memory in the machine. And please send me your
> .config, off-list.
>
> Thanks.
> -
> To unsubscribe from this list: send the line
> "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs
http://hotjobs.sweepstakes.yahoo.com/careermakeover
next prev parent reply other threads:[~2004-04-28 7:29 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 [this message]
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
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=20040428072918.56419.qmail@web90007.mail.scd.yahoo.com \
--to=phyprabab@yahoo.com \
--cc=akpm@osdl.org \
--cc=busterbcook@yahoo.com \
--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
all inboxes | Powered by JetHome®