From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: New package of beta-level NFS client updates out for 2.4.19-rc1
Date: Mon, 8 Jul 2002 19:29:43 +0200 [thread overview]
Message-ID: <agcjiv$hpi$2@main.gmane.org> (raw)
Hi,
There's a new NFS_ALL package full of NFS client updates out for 2.4.19-rc1.
New features include:
- UDP message round trip timing in order to improve the timeout + resend
cycle.
- UDP congestion control as per Van Jacobson.
- Further improvements to the close-to-open code
- Full support for the NFSv3 ACCESS function (as required by people who want
to use ACLs).
A full description of all the components and features can be found in the file
http://www.fys.uio.no/~trondmy/src/2.4.19-rc1/HEADER.html
the patch itself can be found as
http://www.fys.uio.no/~trondmy/src/2.4.19-rc1/linux-2.4.19-NFS_ALL.dif
For those who have been following the contents of these files, please note
that a lot of changes have been made w.r.t. the 2.4.18 version:
Amongst other things, the 'ping' patch (see
http://www.fys.uio.no/~trondmy/src/2.4.18/HEADER.html) is assumed to be
replaced by the new and improved RPC round trip timing+congestion avoidance
code.
The DIRECTIO patch has been removed pending a decision by Chuck on whether or
not he wants to continue supporting it?
Happy testing,
Trond
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Oh, it's good to be a geek.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2002-07-08 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-08 17:29 Trond Myklebust [this message]
[not found] <200207081929.43742.trond.myklebust@fys.uio.no>
2002-07-09 9:13 ` New package of beta-level NFS client updates out for 2.4.19-rc1 Trond Myklebust
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='agcjiv$hpi$2@main.gmane.org' \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
/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