From: Chuck Lever <chuck.lever@oracle.com>
To: steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 0/4] Handle "proto=rdma" regressions
Date: Tue, 07 Sep 2010 12:25:55 -0400 [thread overview]
Message-ID: <20100907162156.3392.90376.stgit@seurat.1015granger.net> (raw)
Steve-
This series is entirely untested, and is meant to be only an example
of how we could handle "proto=rdma" and "rdma" in mount.nfs.
The last patch in the series may not work at all. It depends on the
kernel returning EPROTONOSUPPORT for "vers=4,rdma".
---
Chuck Lever (4):
mount.nfs: Prepare way for "vers=4,rdma" mounts
mount.nfs: Support an "rdma" mount option
mount.nfs: Use nfs_nfs_protocol() for checking for proto=rdma
getport: Recognize "rdma" and "rdma6" netid
support/include/nfsrpc.h | 6 ++++++
support/nfs/getport.c | 25 +++++++++++++++++++++++++
utils/mount/network.c | 9 +++++++--
utils/mount/nfs.man | 11 ++++++++++-
utils/mount/stropts.c | 16 ++++++++--------
5 files changed, 56 insertions(+), 11 deletions(-)
--
Chuck Lever
next reply other threads:[~2010-09-07 16:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 16:25 Chuck Lever [this message]
2010-09-07 16:26 ` [PATCH 1/4] getport: Recognize "rdma" and "rdma6" netid Chuck Lever
2010-09-07 16:26 ` [PATCH 2/4] mount.nfs: Use nfs_nfs_protocol() for checking for proto=rdma Chuck Lever
2010-09-07 16:26 ` [PATCH 3/4] mount.nfs: Support an "rdma" mount option Chuck Lever
2010-09-07 16:26 ` [PATCH 4/4] mount.nfs: Prepare way for "vers=4,rdma" mounts Chuck Lever
[not found] ` <20100907162638.3392.14786.stgit-x+BlCsqV7M/wdl/1UfZZQIVfYA8g3rJ/@public.gmane.org>
2010-09-07 20:07 ` Steve Dickson
2010-09-07 20:14 ` Chuck Lever
2010-09-07 20:30 ` Steve Dickson
2010-09-07 17:57 ` [PATCH 0/4] Handle "proto=rdma" regressions Steve Dickson
2010-09-07 19:21 ` Chuck Lever
2010-09-08 16:22 ` Steve Dickson
2010-09-09 14:50 ` Steve Dickson
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=20100907162156.3392.90376.stgit@seurat.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.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