From: "H. J. Lu" <hjl@lucon.org>
To: Bryan O'Sullivan <bos@serpentine.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
"Heflin, Roger A." <Roger.A.Heflin@conoco.com>,
nfs@lists.sourceforge.net
Subject: Re: 2.4.19 NFSALL performance oddity
Date: Sat, 5 Oct 2002 21:09:57 -0700 [thread overview]
Message-ID: <20021005210957.A23389@lucon.org> (raw)
In-Reply-To: <1033876862.18607.0.camel@camp4.serpentine.com>; from bos@serpentine.com on Sat, Oct 05, 2002 at 09:01:02PM -0700
On Sat, Oct 05, 2002 at 09:01:02PM -0700, Bryan O'Sullivan wrote:
> On Sat, 2002-10-05 at 16:41, H. J. Lu wrote:
>
> > It must be a new bug. I used to have Quad P/II Xeon with 8GB RAM.
> > I had no problem with its NFS server performance. Also my modified
> > kernel based on RedHat kernel 2.4.18-14 has no NFS server problem
> > with 1.5GB RAM.
>
> You're not using Trond's NFS_ALL patch, though, right? That has some
> substantial modifications to the source.
>
RedHat 2.4.18-14 is kernel 2.4.18 + tons of patches. I don't think
it has straight Trond's NFS_ALL patch. But it does have some NFS
changes. The only NFS related complaint I have is they default the
NFS V3 block size to 4096 which kills the NFS client performance. I
believe they put that in to avoid crashing NetApp. I changed it to
8192 and I am quite happy with its NFS performance.
H.J.
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-10-06 4:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-04 21:45 2.4.19 NFSALL performance oddity Heflin, Roger A.
2002-10-04 23:46 ` Trond Myklebust
2002-10-05 4:48 ` Bryan O'Sullivan
2002-10-05 16:18 ` Trond Myklebust
2002-10-05 20:55 ` Bryan O'Sullivan
2002-10-05 21:51 ` Trond Myklebust
2002-10-05 23:41 ` H. J. Lu
2002-10-06 4:01 ` Bryan O'Sullivan
2002-10-06 4:09 ` H. J. Lu [this message]
2002-10-06 4:16 ` Bryan O'Sullivan
-- strict thread matches above, loose matches on Subject: below --
2002-10-06 1:56 Heflin, Roger A.
2002-10-07 21:27 Heflin, Roger A.
2002-10-07 22:20 ` Trond Myklebust
2002-10-08 20:53 Heflin, Roger A.
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=20021005210957.A23389@lucon.org \
--to=hjl@lucon.org \
--cc=Roger.A.Heflin@conoco.com \
--cc=bos@serpentine.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/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.