From: Shirley Ma <shirley.ma@oracle.com>
To: Bruce Fields <bfields@redhat.com>
Cc: leon@leon.nu, Chuck Lever <Chuck.Lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
linux-rdma <linux-rdma@vger.kernel.org>
Subject: [PATCH] Documentation nfs-rdma.txt: Update nfs-rdma kernel module name and add IPv6 addressing option rdma6
Date: Mon, 04 Apr 2016 15:08:02 -0700 [thread overview]
Message-ID: <5702E5C2.8090007@oracle.com> (raw)
In-Reply-To: <5702CD3B.4030207@oracle.com>
Update NFS/RDMA transport module name from client xprtrdma,
server svcrdma to rpcrdma which supports both server and client.
Add mount proto option rdma6 to use IPv6 addressing for NFS/RDMA.
Signed-off-by: Shirley Ma <shirley.ma@oracle.com>
---
Documentation/filesystems/nfs/nfs-rdma.txt | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/Documentation/filesystems/nfs/nfs-rdma.txt b/Documentation/filesystems/nfs/nfs-rdma.txt
index 1e65645..6101b57 100644
--- a/Documentation/filesystems/nfs/nfs-rdma.txt
+++ b/Documentation/filesystems/nfs/nfs-rdma.txt
@@ -238,12 +238,13 @@ NFS/RDMA Setup
- Start the NFS server
- If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
- kernel config), load the RDMA transport module:
+ If the NFS/RDMA was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
+ kernel config), load the RDMA transport module which supports both client
+ and server:
- $ modprobe svcrdma
+ $ modprobe rpcrdma
- Regardless of how the server was built (module or built-in), start the
+ Regardless of how the rpcrdma was built (module or built-in), start the
server:
$ /etc/init.d/nfs start
@@ -258,15 +259,14 @@ NFS/RDMA Setup
- On the client system
- If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
- kernel config), load the RDMA client module:
+ Regardless of how rpcrdma was built (module or built-in), use this command
+ to mount the NFS/RDMA server through IPv4 addressing:
- $ modprobe xprtrdma.ko
+ $ mount -o rdma,port=20049 <IPoIB-server-name-or-IPv4-address>:/<export> /mnt
- Regardless of how the client was built (module or built-in), use this
- command to mount the NFS/RDMA server:
+ or through IPv6 addressing
- $ mount -o rdma,port=20049 <IPoIB-server-name-or-address>:/<export> /mnt
+ $ mount -o rdma6,port=20049 [<IPoIB-server-name-or-IPv6-address>]:/<export> /mnt
To verify that the mount is using RDMA, run "cat /proc/mounts" and check
the "proto" field for the given mount.
prev parent reply other threads:[~2016-04-04 22:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 18:30 [PATCH] nfs: add nfs IPv6 rdma6 mount option support Shirley Ma
2016-03-16 18:46 ` J. Bruce Fields
2016-03-22 19:38 ` Anna Schumaker
2016-03-22 21:24 ` Chuck Lever
2016-03-22 21:46 ` Trond Myklebust
2016-03-22 21:52 ` Chuck Lever
2016-03-22 21:55 ` Trond Myklebust
2016-03-22 22:01 ` Chuck Lever
2016-03-23 18:03 ` Shirley Ma
2016-04-04 18:15 ` [PATCH V2] nfs: add mount proto=rdma6 option for NFS/RDMA IPv6 addressing Shirley Ma
2016-04-04 19:50 ` Leon Romanovsky
2016-04-04 20:23 ` Shirley Ma
2016-04-04 22:08 ` Shirley Ma [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=5702E5C2.8090007@oracle.com \
--to=shirley.ma@oracle.com \
--cc=Chuck.Lever@oracle.com \
--cc=bfields@redhat.com \
--cc=leon@leon.nu \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-rdma@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;
as well as URLs for NNTP newsgroup(s).