From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: Rex Dieter <rdieter@math.unl.edu>
Cc: nfs@lists.sourceforge.net
Subject: Re: RH 7.3 kernels and NFS performance
Date: Wed, 7 Aug 2002 15:04:05 -0400 [thread overview]
Message-ID: <20020807150405.B25584@ti19> (raw)
In-Reply-To: <Pine.LNX.4.44.0208071142060.1462-100000@duran.unl.edu>; from rdieter@math.unl.edu on Wed, Aug 07, 2002 at 11:43:24AM -0500
On Wed, Aug 07, 2002 at 11:43:24AM -0500, Rex Dieter wrote:
> I just tested things with a test kernel (2.4.18-7) from redhat, and it
> sync write speeds were again way up there. Problem fixed, as far as I'm
> concerned... hopefully, they'll release an errata soon.
BTW, Arjan has included many of Trond's RPC patches in the latest
Rawhide kernels:
$ rpm -qp --changelog kernel-2.4.18-7.93.src.rpm | head -4
* Fri Aug 02 2002 Arjan van de Ven <arjanv@redhat.com>
- added most of the NFS patchkit
Based on the patch file names, these look like Trond's 2.4.19-rc3 patches:
linux-2.4.19-00-fix_clnt.patch
linux-2.4.19-01-fix_kmap1.patch
linux-2.4.19-02-fix_kmap2.patch
linux-2.4.19-03-fix_kmap3.patch
linux-2.4.19-04-rpc_rep.patch
linux-2.4.19-05-rpc_rtt1.patch
linux-2.4.19-06-rpc_rtt2.patch
linux-2.4.19-07-rpc_rtt3.patch
linux-2.4.19-08-xprt_write.patch
linux-2.4.19-09-rpc_cong1.patch
linux-2.4.19-10-rpc_cong2.patch
linux-2.4.19-11-rpc_cong3.patch
linux-2.4.19-12-rpc_wspace.patch
linux-2.4.19-13-rpc_cleanup.patch
linux-2.4.19-16-rpcbuf.patch
This should be nearly current, though Trond's 2.4.19 patches are broken
down somewhat differently.
I hope that Trond is planning to submit most of this to Marcelo for
2.4.20, as Neil is submitting his NFS server patches, and it would be
very nice to have a 2.4.20 that is fully up-to-date w.r.t current NFS
patches for both client and server. [Those of us on this list for a
long time will remember a similar exercise with Alan for 2.2.19 --
gosh, that seems like ancient history. :-P]
In any case, Trond's work should receive some more widespread "end-user"
testing from the Limbo Beta and Rawhide crowd in the near future.
I've long pined [since RH 5.x] for a Red Hat kernel with working
NFS that played nice with the NetApp and Solaris. It has since become
a ritual to patch NFS into the Red Hat tree.
Many thanks to Trond and Neil for their tireless efforts!
It is difficult to underestimate how important working NFS is in deployments
like ours ...
Regards
Bill Rugolsky
-------------------------------------------------------
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-08-07 19:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-07 15:35 RH 7.3 kernels and NFS performance Jeff Layton
2002-08-07 15:37 ` Rex Dieter
2002-08-07 15:55 ` Trond Myklebust
2002-08-07 16:05 ` Rex Dieter
2002-08-07 16:17 ` Trond Myklebust
2002-08-07 16:21 ` Rex Dieter
2002-08-07 16:25 ` Trond Myklebust
2002-08-07 16:43 ` Rex Dieter
2002-08-07 17:19 ` Tom McNeal
2002-08-07 19:04 ` Bill Rugolsky Jr. [this message]
2002-08-08 5:08 ` Seth Vidal
2002-08-08 11:56 ` Rex Dieter
-- strict thread matches above, loose matches on Subject: below --
2002-08-07 15:45 Lever, Charles
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=20020807150405.B25584@ti19 \
--to=brugolsky@telemetry-investments.com \
--cc=nfs@lists.sourceforge.net \
--cc=rdieter@math.unl.edu \
/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.