From: Steve Dickson <steved@redhat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: [PATCH 3/3] Document the rdma mount option in the nfs man page
Date: Tue, 7 Sep 2010 16:22:01 -0400 [thread overview]
Message-ID: <1283890921-3447-4-git-send-email-steved@redhat.com> (raw)
In-Reply-To: <1283890921-3447-1-git-send-email-steved@redhat.com>
Co-Authored-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Steve Dickson <steved@redhat.com>
---
utils/mount/nfs.man | 14 +++++++++++++-
1 files changed, 13 insertions(+), 1 deletions(-)
diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index 3806635..8964512 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -495,9 +495,15 @@ command,
.I netid
is a valid netid listed in
.IR /etc/netconfig .
-Otherwise,
+The value "rdma" may also be specified.
+If the
+.B mount.nfs
+command does not have TI-RPC support, then
.I netid
is one of "tcp," "udp," or "rdma," and only IPv4 may be used.
+Also with "rdma" the version 3 NFS protocol will be used
+unless a different protocol is specified on the command
+line.
.IP
Each transport protocol uses different default
.B retrans
@@ -537,6 +543,12 @@ option is an alternative to specifying
.BR proto=tcp.
It is included for compatibility with other operating systems.
.TP 1.5i
+.B rdma
+The
+.B rdma
+option is an alternative to specifying
+.BR proto=rdma.
+.TP 1.5i
.BI port= n
The numeric value of the server's NFS service port.
If the server's NFS service is not available on the specified port,
--
1.7.2.1
prev parent reply other threads:[~2010-09-07 20:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 20:21 [PATCH 0/3] mount: Updated RDMA processing in the mount command Steve Dickson
2010-09-07 20:21 ` [PATCH 1/3] Added support for the the -o rdma option Steve Dickson
2010-09-07 20:22 ` [PATCH 2/3] Ensure the corrrect address family is used on RDMA mounts Steve Dickson
2010-09-07 20:22 ` Steve Dickson [this message]
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=1283890921-3447-4-git-send-email-steved@redhat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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