From: "J. Bruce Fields" <bfields@fieldses.org>
To: linux-nfs@vger.kernel.org
Cc: Tom Tucker <tom@opengridcomputing.com>
Subject: 4.1 and rdma
Date: Tue, 14 Dec 2010 16:03:10 -0500 [thread overview]
Message-ID: <20101214210310.GI24828@fieldses.org> (raw)
I asked Tom Tucker what he thought would be the minimum needed for our
4.1 implementation to be up-to-spec with regard to RDMA, and he took a
first look through the spec and made some notes:
http://wiki.linux-nfs.org/wiki/index.php/4.1_RDMA_issues
I don't know any big rush for 4.1/rdma, just wanted to make sure we
weren't doing anything that would make it hard to do it right later.
On the server side I think the safest thing to do may be just to return
an error on a CREATE_SESSION that arrives over an rdma connection, at
least until we figure out what more we'd need to do to support it
correctly?
--b.
reply other threads:[~2010-12-14 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20101214210310.GI24828@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=tom@opengridcomputing.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;
as well as URLs for NNTP newsgroup(s).