From: "Mike Snitzer" <snitzer@gmail.com>
To: chuck.lever@oracle.com
Cc: "Roland Dreier" <rdreier@cisco.com>, NeilBrown <neilb@suse.de>,
"Andrew Morton" <akpm@osdl.org>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: Merge plans for RPC/RDMA? (Was: Re: [NFS] [PATCH 000 of 14] knfsd: Preparation for IPv6 support in NFS server.)
Date: Fri, 13 Apr 2007 20:04:10 -0400 [thread overview]
Message-ID: <170fa0d20704131704y13151149n817cd698e22781c8@mail.gmail.com> (raw)
In-Reply-To: <46200822.5060800@oracle.com>
On 4/13/07, Chuck Lever <chuck.lever@oracle.com> wrote:
> Mike Snitzer wrote:
> > On 2/2/07, Chuck Lever <chuck.lever@oracle.com> wrote:
> >> Roland Dreier wrote:
> >> > > They are mostly from Chuck Level and make preparating for IPv6
> >> support
> >> > > in the NFS server.
> >> > > They are *not* for 2.6.20, but should be ok for .21.
> >> >
> >> > Out of curiousity, does this patch series reduce the delta between the
> >> > NFS/RDMA tree and mainline Linux? In other words does this bring
> >> > NFS/RDMA closer to merging?
> >>
> >> Hi Roland-
> >>
> >> The client side support for an RPC/RDMA module is almost completely
> >> integrated into mainline. There is still a minimal set of patches
> >> required to support alternate transports in loadable kernel modules
> >> which Trond has indicated he will integrate when the RPC/RDMA transport
> >> is ready to be integrated.
> >
> > Hi Chuck,
> >
> > I must be missing something because I don't see _any_ trace of the
> > core RPC over RDMA support (xprtrdma et al), your RPC Transport
> > Switch, or any of the other supporting changes in mainline. Could
> > you, or others, please clarify the plan for merging RPC/RDMA?
>
> The RPC transport switch patches are almost fully integrated into
> mainline. The xprtrdma piece is what is not there yet.
OK, has the xprtrdma piece been reviewed by the community? What, if
anything, is preventing the code from being included in -mm for wider
testing?
Has xprtrdma inclusion/progress been discussed on some other mailing
list? Any insight would be appreciated.
next prev parent reply other threads:[~2007-04-14 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 20:47 Mike Snitzer
2007-04-13 22:14 ` [NFS] Merge plans for RPC/RDMA? (Was: " Trond Myklebust
2007-04-15 3:40 ` Mike Snitzer
2007-04-16 14:13 ` James Lentini
2007-04-16 14:48 ` Mike Snitzer
2007-04-13 22:45 ` Merge plans for RPC/RDMA? (Was: Re: [NFS] " Chuck Lever
2007-04-14 0:04 ` Mike Snitzer [this message]
2007-04-14 1:07 ` Chuck Lever
2007-04-14 1:14 ` Chuck Lever
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=170fa0d20704131704y13151149n817cd698e22781c8@mail.gmail.com \
--to=snitzer@gmail.com \
--cc=akpm@osdl.org \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.net \
--cc=rdreier@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®