From: Chris Mason <mason@suse.com>
To: Brian Ristuccia <bristucc@sw.starentnetworks.com>,
linux-kernel@vger.kernel.org
Subject: Re: kernel nfsd consuming 100% CPU on 2.4.17 and 2.4.18 with reiserfs?
Date: Tue, 26 Feb 2002 09:55:55 -0500 [thread overview]
Message-ID: <2305220000.1014735355@tiny> (raw)
In-Reply-To: <3C7B9212.5050400@sw.starentnetworks.com>
In-Reply-To: <3C7B9212.5050400@sw.starentnetworks.com>
On Tuesday, February 26, 2002 08:48:02 AM -0500 Brian Ristuccia
<bristucc@sw.starentnetworks.com> wrote:
> It seems that kernel nfsd consumes an inordinate amount of CPU time
> during writes on this machine. With a few hundred kb/sec being written
> over NFSv3 from a 2.2.17 client, all of the nfsd threads each consume as
> much of the available CPU time as possible. On a similarly configured
> machine with ext3 instead of reiserfs, nfsd consumes much less CPU time.
>
> Is there a known issue with NFSv3 performance and reiserfs?
No, it is not a known issue. Does it only happen with a 2.2.17 client, or
can you reproduce with any kernel version on the client?
-chris
next prev parent reply other threads:[~2002-02-26 14:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-26 13:48 Brian Ristuccia
2002-02-26 14:55 ` Chris Mason [this message]
2002-02-26 15:09 ` Brian Ristuccia
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=2305220000.1014735355@tiny \
--to=mason@suse.com \
--cc=bristucc@sw.starentnetworks.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®