From: Chris Croswhite <csc@cadence.com>
To: Chuck Lever <chucklever@gmail.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>
Subject: Re: cel's patches for 2.6.18 kernels
Date: Wed, 20 Sep 2006 17:06:10 -0700 [thread overview]
Message-ID: <1158797170.6331.109.camel@rcs004> (raw)
In-Reply-To: <76bd70e30609201353l7d8c063fp94916c509b08b24e@mail.gmail.com>
ET3.1.7a is installed for linux only. Solaris and AIX will be later
tonight.
Chris
On Wed, 2006-09-20 at 13:53, Chuck Lever wrote:
> On 9/20/06, Christoph Hellwig <hch@infradead.org> wrote:
> > On Wed, Sep 20, 2006 at 02:28:10PM -0400, Chuck Lever wrote:
> > > This e-mail announces the release of cel's patch set for Linux 2.6.18
> > > kernels. The patchset contains several important features, including:
> > >
> > > 1. The finishing patches for the RPC client transport switch
> > >
> > > 2. Support for rpcbind protocol versions 2 and 3
> > >
> > > 3. Some support for IPv6 in the RPC and NFS clients
> > >
> > > 4. Elimination of the BKL in the RPC and NFS clients
> > >
> > > 5. Elimination of the RPC slot table
> >
> > What's the merge plan for those patches? The transport switch and ipv6
> > code is eagerly anticipated by many people.
>
> About two thirds of the RPC transport switch is already in.
> Twenty-ish more patches are going in 2.6.19. There remain roughly 30
> more patches that I need to walk through with Trond, and we can
> probably get those into 2.6.20. I wouldn't mind moving them up, but
> that's up to Trond.
>
> The IPv6 stuff is still being finished. Olaf may be able to help with
> the NLM parts; Bull is still working through the NFS server parts; I'm
> trying to act as integrator. I would like to line up some testers. I
> think those may be as far out as three or four releases, but progress
> is occurring -- note there are a lot more IPv6 patches in this
> patchset than there were in 2.6.17's.
>
> Elimination of the BKL is complete except for a few unimportant spots.
> All it needs is thorough testing on a multi-way ppc64 system to
> reveal niggling problems.
>
> The RPC slot table patches are completely rewritten in this release.
> That will probably need some testing and review.
>
> --
> "We who cut mere stones must always be envisioning cathedrals"
> -- Quarry worker's creed
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-09-21 0:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-20 18:28 cel's patches for 2.6.18 kernels Chuck Lever
2006-09-20 20:20 ` Christoph Hellwig
2006-09-20 20:53 ` Chuck Lever
2006-09-20 21:16 ` Trond Myklebust
2006-09-21 2:29 ` Chuck Lever
2006-09-21 12:26 ` Steve Dickson
2006-09-21 13:47 ` Trond Myklebust
2006-09-21 14:50 ` Chuck Lever
2006-09-21 15:06 ` Trond Myklebust
2006-09-21 15:51 ` Chuck Lever
2006-09-21 17:21 ` Trond Myklebust
2006-09-21 17:33 ` Chuck Lever
2006-09-21 17:33 ` Trond Myklebust
2006-09-21 17:37 ` Chuck Lever
2006-09-21 17:41 ` Trond Myklebust
2006-09-21 0:06 ` Chris Croswhite [this message]
2006-09-21 13:48 ` Tony Reix
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=1158797170.6331.109.camel@rcs004 \
--to=csc@cadence.com \
--cc=chucklever@gmail.com \
--cc=hch@infradead.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 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.