nfs-rdma.txt 9.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275
  1. ################################################################################
  2. # #
  3. # NFS/RDMA README #
  4. # #
  5. ################################################################################
  6. Author: NetApp and Open Grid Computing
  7. Date: May 29, 2008
  8. Table of Contents
  9. ~~~~~~~~~~~~~~~~~
  10. - Overview
  11. - Getting Help
  12. - Installation
  13. - Check RDMA and NFS Setup
  14. - NFS/RDMA Setup
  15. Overview
  16. ~~~~~~~~
  17. This document describes how to install and setup the Linux NFS/RDMA client
  18. and server software.
  19. The NFS/RDMA client was first included in Linux 2.6.24. The NFS/RDMA server
  20. was first included in the following release, Linux 2.6.25.
  21. In our testing, we have obtained excellent performance results (full 10Gbit
  22. wire bandwidth at minimal client CPU) under many workloads. The code passes
  23. the full Connectathon test suite and operates over both Infiniband and iWARP
  24. RDMA adapters.
  25. Getting Help
  26. ~~~~~~~~~~~~
  27. If you get stuck, you can ask questions on the
  28. nfs-rdma-devel@lists.sourceforge.net
  29. mailing list.
  30. Installation
  31. ~~~~~~~~~~~~
  32. These instructions are a step by step guide to building a machine for
  33. use with NFS/RDMA.
  34. - Install an RDMA device
  35. Any device supported by the drivers in drivers/infiniband/hw is acceptable.
  36. Testing has been performed using several Mellanox-based IB cards, the
  37. Ammasso AMS1100 iWARP adapter, and the Chelsio cxgb3 iWARP adapter.
  38. - Install a Linux distribution and tools
  39. The first kernel release to contain both the NFS/RDMA client and server was
  40. Linux 2.6.25 Therefore, a distribution compatible with this and subsequent
  41. Linux kernel release should be installed.
  42. The procedures described in this document have been tested with
  43. distributions from Red Hat's Fedora Project (http://fedora.redhat.com/).
  44. - Install nfs-utils-1.1.2 or greater on the client
  45. An NFS/RDMA mount point can be obtained by using the mount.nfs command in
  46. nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils
  47. version with support for NFS/RDMA mounts, but for various reasons we
  48. recommend using nfs-utils-1.1.2 or greater). To see which version of
  49. mount.nfs you are using, type:
  50. $ /sbin/mount.nfs -V
  51. If the version is less than 1.1.2 or the command does not exist,
  52. you should install the latest version of nfs-utils.
  53. Download the latest package from:
  54. http://www.kernel.org/pub/linux/utils/nfs
  55. Uncompress the package and follow the installation instructions.
  56. If you will not need the idmapper and gssd executables (you do not need
  57. these to create an NFS/RDMA enabled mount command), the installation
  58. process can be simplified by disabling these features when running
  59. configure:
  60. $ ./configure --disable-gss --disable-nfsv4
  61. To build nfs-utils you will need the tcp_wrappers package installed. For
  62. more information on this see the package's README and INSTALL files.
  63. After building the nfs-utils package, there will be a mount.nfs binary in
  64. the utils/mount directory. This binary can be used to initiate NFS v2, v3,
  65. or v4 mounts. To initiate a v4 mount, the binary must be called
  66. mount.nfs4. The standard technique is to create a symlink called
  67. mount.nfs4 to mount.nfs.
  68. This mount.nfs binary should be installed at /sbin/mount.nfs as follows:
  69. $ sudo cp utils/mount/mount.nfs /sbin/mount.nfs
  70. In this location, mount.nfs will be invoked automatically for NFS mounts
  71. by the system mount command.
  72. NOTE: mount.nfs and therefore nfs-utils-1.1.2 or greater is only needed
  73. on the NFS client machine. You do not need this specific version of
  74. nfs-utils on the server. Furthermore, only the mount.nfs command from
  75. nfs-utils-1.1.2 is needed on the client.
  76. - Install a Linux kernel with NFS/RDMA
  77. The NFS/RDMA client and server are both included in the mainline Linux
  78. kernel version 2.6.25 and later. This and other versions of the 2.6 Linux
  79. kernel can be found at:
  80. ftp://ftp.kernel.org/pub/linux/kernel/v2.6/
  81. Download the sources and place them in an appropriate location.
  82. - Configure the RDMA stack
  83. Make sure your kernel configuration has RDMA support enabled. Under
  84. Device Drivers -> InfiniBand support, update the kernel configuration
  85. to enable InfiniBand support [NOTE: the option name is misleading. Enabling
  86. InfiniBand support is required for all RDMA devices (IB, iWARP, etc.)].
  87. Enable the appropriate IB HCA support (mlx4, mthca, ehca, ipath, etc.) or
  88. iWARP adapter support (amso, cxgb3, etc.).
  89. If you are using InfiniBand, be sure to enable IP-over-InfiniBand support.
  90. - Configure the NFS client and server
  91. Your kernel configuration must also have NFS file system support and/or
  92. NFS server support enabled. These and other NFS related configuration
  93. options can be found under File Systems -> Network File Systems.
  94. - Build, install, reboot
  95. The NFS/RDMA code will be enabled automatically if NFS and RDMA
  96. are turned on. The NFS/RDMA client and server are configured via the hidden
  97. SUNRPC_XPRT_RDMA config option that depends on SUNRPC and INFINIBAND. The
  98. value of SUNRPC_XPRT_RDMA will be:
  99. - N if either SUNRPC or INFINIBAND are N, in this case the NFS/RDMA client
  100. and server will not be built
  101. - M if both SUNRPC and INFINIBAND are on (M or Y) and at least one is M,
  102. in this case the NFS/RDMA client and server will be built as modules
  103. - Y if both SUNRPC and INFINIBAND are Y, in this case the NFS/RDMA client
  104. and server will be built into the kernel
  105. Therefore, if you have followed the steps above and turned no NFS and RDMA,
  106. the NFS/RDMA client and server will be built.
  107. Build a new kernel, install it, boot it.
  108. Check RDMA and NFS Setup
  109. ~~~~~~~~~~~~~~~~~~~~~~~~
  110. Before configuring the NFS/RDMA software, it is a good idea to test
  111. your new kernel to ensure that the kernel is working correctly.
  112. In particular, it is a good idea to verify that the RDMA stack
  113. is functioning as expected and standard NFS over TCP/IP and/or UDP/IP
  114. is working properly.
  115. - Check RDMA Setup
  116. If you built the RDMA components as modules, load them at
  117. this time. For example, if you are using a Mellanox Tavor/Sinai/Arbel
  118. card:
  119. $ modprobe ib_mthca
  120. $ modprobe ib_ipoib
  121. If you are using InfiniBand, make sure there is a Subnet Manager (SM)
  122. running on the network. If your IB switch has an embedded SM, you can
  123. use it. Otherwise, you will need to run an SM, such as OpenSM, on one
  124. of your end nodes.
  125. If an SM is running on your network, you should see the following:
  126. $ cat /sys/class/infiniband/driverX/ports/1/state
  127. 4: ACTIVE
  128. where driverX is mthca0, ipath5, ehca3, etc.
  129. To further test the InfiniBand software stack, use IPoIB (this
  130. assumes you have two IB hosts named host1 and host2):
  131. host1$ ip link set dev ib0 up
  132. host1$ ip address add dev ib0 a.b.c.x
  133. host2$ ip link set dev ib0 up
  134. host2$ ip address add dev ib0 a.b.c.y
  135. host1$ ping a.b.c.y
  136. host2$ ping a.b.c.x
  137. For other device types, follow the appropriate procedures.
  138. - Check NFS Setup
  139. For the NFS components enabled above (client and/or server),
  140. test their functionality over standard Ethernet using TCP/IP or UDP/IP.
  141. NFS/RDMA Setup
  142. ~~~~~~~~~~~~~~
  143. We recommend that you use two machines, one to act as the client and
  144. one to act as the server.
  145. One time configuration:
  146. - On the server system, configure the /etc/exports file and
  147. start the NFS/RDMA server.
  148. Exports entries with the following formats have been tested:
  149. /vol0 192.168.0.47(fsid=0,rw,async,insecure,no_root_squash)
  150. /vol0 192.168.0.0/255.255.255.0(fsid=0,rw,async,insecure,no_root_squash)
  151. The IP address(es) is(are) the client's IPoIB address for an InfiniBand
  152. HCA or the client's iWARP address(es) for an RNIC.
  153. NOTE: The "insecure" option must be used because the NFS/RDMA client does
  154. not use a reserved port.
  155. Each time a machine boots:
  156. - Load and configure the RDMA drivers
  157. For InfiniBand using a Mellanox adapter:
  158. $ modprobe ib_mthca
  159. $ modprobe ib_ipoib
  160. $ ip li set dev ib0 up
  161. $ ip addr add dev ib0 a.b.c.d
  162. NOTE: use unique addresses for the client and server
  163. - Start the NFS server
  164. If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
  165. kernel config), load the RDMA transport module:
  166. $ modprobe svcrdma
  167. Regardless of how the server was built (module or built-in), start the
  168. server:
  169. $ /etc/init.d/nfs start
  170. or
  171. $ service nfs start
  172. Instruct the server to listen on the RDMA transport:
  173. $ echo rdma 20049 > /proc/fs/nfsd/portlist
  174. - On the client system
  175. If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
  176. kernel config), load the RDMA client module:
  177. $ modprobe xprtrdma.ko
  178. Regardless of how the client was built (module or built-in), use this
  179. command to mount the NFS/RDMA server:
  180. $ mount -o rdma,port=20049 <IPoIB-server-name-or-address>:/<export> /mnt
  181. To verify that the mount is using RDMA, run "cat /proc/mounts" and check
  182. the "proto" field for the given mount.
  183. Congratulations! You're using NFS/RDMA!