From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Mike Snitzer <snitzer@gmail.com>
Cc: chuck.lever@oracle.com, NeilBrown <neilb@suse.de>,
Andrew Morton <akpm@osdl.org>, Roland Dreier <rdreier@cisco.com>,
nfs@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [NFS] Merge plans for RPC/RDMA? (Was: Re: [PATCH 000 of 14] knfsd: Preparation for IPv6 support in NFS server.)
Date: Fri, 13 Apr 2007 18:14:25 -0400 [thread overview]
Message-ID: <1176502465.6394.26.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <170fa0d20704131347u4a28b5d1h1959227980449fbf@mail.gmail.com>
On Fri, 2007-04-13 at 16:47 -0400, Mike Snitzer wrote:
> 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?
That would be a question for the actual RPC/RDMA developers (i.e. James
Lentini and Tom Talpey). They haven't submitted any code for review yet.
> Do you mean the NFS/RDMA server code from Tom Tucker of Open Grid
> Computing? Why wouldn't this code be included?
That too has never been submitted for review AFAIK. Why would we include
it?
Cheers
Trond
next prev parent reply other threads:[~2007-04-13 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-13 20:47 Merge plans for RPC/RDMA? (Was: Re: [NFS] " Mike Snitzer
2007-04-13 22:14 ` Trond Myklebust [this message]
2007-04-15 3:40 ` [NFS] Merge plans for RPC/RDMA? (Was: " 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
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=1176502465.6394.26.camel@heimdal.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--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 \
--cc=snitzer@gmail.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®