aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--Documentation/filesystems/nfs-rdma.txt40
1 files changed, 21 insertions, 19 deletions
diff --git a/Documentation/filesystems/nfs-rdma.txt b/Documentation/filesystems/nfs-rdma.txt
index 9ad453d4891a..44bd766f2e5d 100644
--- a/Documentation/filesystems/nfs-rdma.txt
+++ b/Documentation/filesystems/nfs-rdma.txt
@@ -63,10 +63,10 @@ Installation
63 - Install nfs-utils-1.1.2 or greater on the client 63 - Install nfs-utils-1.1.2 or greater on the client
64 64
65 An NFS/RDMA mount point can be obtained by using the mount.nfs command in 65 An NFS/RDMA mount point can be obtained by using the mount.nfs command in
66 nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils version 66 nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils
67 with support for NFS/RDMA mounts, but for various reasons we recommend using 67 version with support for NFS/RDMA mounts, but for various reasons we
68 nfs-utils-1.1.2 or greater). To see which version of mount.nfs you are 68 recommend using nfs-utils-1.1.2 or greater). To see which version of
69 using, type: 69 mount.nfs you are using, type:
70 70
71 $ /sbin/mount.nfs -V 71 $ /sbin/mount.nfs -V
72 72
@@ -91,8 +91,9 @@ Installation
91 91
92 After building the nfs-utils package, there will be a mount.nfs binary in 92 After building the nfs-utils package, there will be a mount.nfs binary in
93 the utils/mount directory. This binary can be used to initiate NFS v2, v3, 93 the utils/mount directory. This binary can be used to initiate NFS v2, v3,
94 or v4 mounts. To initiate a v4 mount, the binary must be called mount.nfs4. 94 or v4 mounts. To initiate a v4 mount, the binary must be called
95 The standard technique is to create a symlink called mount.nfs4 to mount.nfs. 95 mount.nfs4. The standard technique is to create a symlink called
96 mount.nfs4 to mount.nfs.
96 97
97 This mount.nfs binary should be installed at /sbin/mount.nfs as follows: 98 This mount.nfs binary should be installed at /sbin/mount.nfs as follows:
98 99
@@ -214,11 +215,11 @@ NFS/RDMA Setup
214 /vol0 192.168.0.47(fsid=0,rw,async,insecure,no_root_squash) 215 /vol0 192.168.0.47(fsid=0,rw,async,insecure,no_root_squash)
215 /vol0 192.168.0.0/255.255.255.0(fsid=0,rw,async,insecure,no_root_squash) 216 /vol0 192.168.0.0/255.255.255.0(fsid=0,rw,async,insecure,no_root_squash)
216 217
217 The IP address(es) is(are) the client's IPoIB address for an InfiniBand HCA or the 218 The IP address(es) is(are) the client's IPoIB address for an InfiniBand
218 cleint's iWARP address(es) for an RNIC. 219 HCA or the cleint's iWARP address(es) for an RNIC.
219 220
220 NOTE: The "insecure" option must be used because the NFS/RDMA client does not 221 NOTE: The "insecure" option must be used because the NFS/RDMA client does
221 use a reserved port. 222 not use a reserved port.
222 223
223 Each time a machine boots: 224 Each time a machine boots:
224 225
@@ -234,12 +235,13 @@ NFS/RDMA Setup
234 235
235 - Start the NFS server 236 - Start the NFS server
236 237
237 If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in kernel config), 238 If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
238 load the RDMA transport module: 239 kernel config), load the RDMA transport module:
239 240
240 $ modprobe svcrdma 241 $ modprobe svcrdma
241 242
242 Regardless of how the server was built (module or built-in), start the server: 243 Regardless of how the server was built (module or built-in), start the
244 server:
243 245
244 $ /etc/init.d/nfs start 246 $ /etc/init.d/nfs start
245 247
@@ -253,17 +255,17 @@ NFS/RDMA Setup
253 255
254 - On the client system 256 - On the client system
255 257
256 If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in kernel config), 258 If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
257 load the RDMA client module: 259 kernel config), load the RDMA client module:
258 260
259 $ modprobe xprtrdma.ko 261 $ modprobe xprtrdma.ko
260 262
261 Regardless of how the client was built (module or built-in), use this command to 263 Regardless of how the client was built (module or built-in), use this
262 mount the NFS/RDMA server: 264 command to mount the NFS/RDMA server:
263 265
264 $ mount -o rdma,port=2050 <IPoIB-server-name-or-address>:/<export> /mnt 266 $ mount -o rdma,port=2050 <IPoIB-server-name-or-address>:/<export> /mnt
265 267
266 To verify that the mount is using RDMA, run "cat /proc/mounts" and check the 268 To verify that the mount is using RDMA, run "cat /proc/mounts" and check
267 "proto" field for the given mount. 269 the "proto" field for the given mount.
268 270
269 Congratulations! You're using NFS/RDMA! 271 Congratulations! You're using NFS/RDMA!