public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Brett E." <brettspamacct@fastclick.com>
To: busterbcook@yahoo.com
Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: pdflush eating a lot of CPU on heavy NFS I/O
Date: Tue, 27 Apr 2004 23:06:39 -0700	[thread overview]
Message-ID: <408F49EF.6020508@fastclick.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0404280009300.28371@ozma.hauschen>

Brent Cook wrote:

>  This didn't seem to be a problem with 2.6.5 or 2.4. Is there something I
> can do to control pdflush or to provide more information?
> 
> Thanks
>  - Brent
> 
Yes regarding controlling pdflush, I don't know about providing pdflush 
information. From Andrew Morton(Thanks Andrew!):

The tunables in /proc/sys/vm are documented in 
Documentation/filesystems/proc.txt.




      parent reply	other threads:[~2004-04-28  6:06 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
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. [this message]

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=408F49EF.6020508@fastclick.com \
    --to=brettspamacct@fastclick.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