From: "J. Bruce Fields" <bfields@fieldses.org>
To: Greg Banks <gnb@sgi.com>
Cc: Thomas Talpey <Thomas.Talpey@netapp.com>,
Linux NFS Mailing List <nfs@lists.sourceforge.net>,
Peter Leckie <pleckie@melbourne.sgi.com>
Subject: Re: [RFC,PATCH 0/14] A transport switch for knfsd
Date: Wed, 16 May 2007 16:53:17 -0400 [thread overview]
Message-ID: <20070516205316.GC18927@fieldses.org> (raw)
In-Reply-To: <20070516191821.GF9626@sgi.com>
On Thu, May 17, 2007 at 05:18:21AM +1000, Greg Banks wrote:
> These 14 patches are an experimental transport switch for knfsd.
> They're based on Tom Tucker's 01-svc-xprt-switch.patch from the
> nfsrdma project November release, but redesigned to provide as simple
> and clean an abstraction as possible to new transport-specific code.
> Various messy details of flags, reference counts and other behaviour
> which are currently redundantly handled in both TCP and UDP code,
> will be handled in generic code now. This makes the task of writing
> new transport code easier and less prone to breakage.
Are there other conjectured future users besides rdma?
What's happened to server-side ipv6, by the way?
--b.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2007-05-16 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 19:18 [RFC,PATCH 0/14] A transport switch for knfsd Greg Banks
2007-05-16 20:53 ` J. Bruce Fields [this message]
2007-05-17 1:36 ` Talpey, Thomas
2007-05-17 7:00 ` Greg Banks
2007-05-17 12:11 ` Talpey, Thomas
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=20070516205316.GC18927@fieldses.org \
--to=bfields@fieldses.org \
--cc=Thomas.Talpey@netapp.com \
--cc=gnb@sgi.com \
--cc=nfs@lists.sourceforge.net \
--cc=pleckie@melbourne.sgi.com \
/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.