public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: 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 12:48:09 -0700	[thread overview]
Message-ID: <20040428124809.418e005d.akpm@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0404280826070.31093@ozma.hauschen>

Brent Cook <busterbcook@yahoo.com> wrote:
>
> On Tue, 27 Apr 2004, Andrew Morton 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.
> 
> Since it was a pretty big deal on my system, I just assumed it was for
> other people's too, and that someone else would have reported it by
> now. I only got concerned when it persisted between rc's.

I think three people have reported it now.

> > > 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.
> 
> Yes, both affected machines had the issue when connecting as a client to a
> 2.4.25-based NFS server.
> 
> > What other filesystems are in use on the client?
> 
> One uses Reiser on /, the other uses ext3 on /. Here is the mount table
> for one machine:

Both machines are exhibiting the problem?

> About 10 minutes into the process, pdflush starts taking over:
> 
>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME CPU COMMAND
>     7 root      25   0     0    0     0 RW   34.4  0.0   3:05   0 pdflush
> 17856 busterb   25   0 69400  65M  5140 R    34.4 26.1   0:31   0 cc1plus
> 19466 busterb   25   0 43732  39M  5140 R    26.3 15.5   0:03   0 cc1plus
> ...
> The network light will flash continually on each machine once pdflush
> gets into this state, which makes me think NFS. Each machine has
> 512-256 MB of ram and a single CPU.

ok..  I spent a couple of hours yesterday trying to get this to happen.  No
joy.  Can't make it happen with your .config either.  I'll set up a 2.4.25
server later on.

What version of gcc are you using?

Could you please capture the contents of /proc/meminfo and /proc/vmstats
when it's happening?

Thanks.

  reply	other threads:[~2004-04-28 20:11 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-28  5:18 pdflush eating a lot of CPU on heavy NFS I/O 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 [this message]
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=20040428124809.418e005d.akpm@osdl.org \
    --to=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