From: Sven Geggus <sven-im-usenet@gegg.us>
To: linux-kernel@vger.kernel.org
Subject: Re: pdflush eating a lot of CPU on heavy NFS I/O
Date: Wed, 28 Apr 2004 12:18:46 +0200 (CEST) [thread overview]
Message-ID: <c6o0e6$2ck$1@benzin.geggus.net> (raw)
In-Reply-To: 20040427230203.1e4693ac.akpm@osdl.org
Andrew Morton <akpm@osdl.org> wrote:
> It's a shame this wasn't reported earlier.
I did report this behaviour in <c6gi0f$g6i$1@benzin.geggus.net> a few days
ago.
> Please confirm that the problem is observed on the NFS client and not the
> NFS server? I'll assume the client.
Shure! The problem is observed on the NFS client, a diskless machine in my
case.
> What other filesystems are in use on the client?
Non in my case!
> Please describe the NFS mount options and the number of CPUs and the amount
> of memory in the machine.
NFS mount options are default and my machine does not use an SMP Kernel (AMD
Athlon 2000+, Single CPU).
Sven
--
/*
* Wirzenius wrote this portably, Torvalds fucked it up :-)
*/ (taken from /usr/src/linux/lib/vsprintf.c)
/me is giggls@ircnet, http://sven.gegg.us/ on the Web
next prev parent reply other threads:[~2004-04-28 10:18 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 [this message]
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='c6o0e6$2ck$1@benzin.geggus.net' \
--to=sven-im-usenet@gegg.us \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.