projects / linux-2.6-block.git / blame
| Commit | Line | Data |
|---|---|---|
| 9098c24f AD |
1 | config SUNRPC |
| 2 | tristate | |
| 3 | ||
| 4 | config SUNRPC_GSS | |
| 5 | tristate | |
| 6 | ||
| 7 | config SUNRPC_XPRT_RDMA | |
| 8 | tristate | |
| 55128bc2 | 9 | depends on SUNRPC && INFINIBAND && INFINIBAND_ADDR_TRANS && EXPERIMENTAL |
| 9098c24f AD |
10 | default SUNRPC && INFINIBAND |
| 11 | help | |
| ce0cf662 BF |
12 | This option allows the NFS client and server to support |
| 13 | an RDMA-enabled transport. | |
| 9098c24f AD |
14 | |
| 15 | To compile RPC client RDMA transport support as a module, | |
| 16 | choose M here: the module will be called xprtrdma. | |
| 17 | ||
| 18 | If unsure, say N. | |
| 19 | ||
| 20 | config SUNRPC_REGISTER_V4 | |
| 21 | bool "Register local RPC services via rpcbind v4 (EXPERIMENTAL)" | |
| 22 | depends on SUNRPC && EXPERIMENTAL | |
| 23 | default n | |
| 24 | help | |
| 25 | Sun added support for registering RPC services at an IPv6 | |
| 26 | address by creating two new versions of the rpcbind protocol | |
| 27 | (RFC 1833). | |
| 28 | ||
| 29 | This option enables support in the kernel RPC server for | |
| 30 | registering kernel RPC services via version 4 of the rpcbind | |
| 31 | protocol. If you enable this option, you must run a portmapper | |
| 32 | daemon that supports rpcbind protocol version 4. | |
| 33 | ||
| 34 | Serving NFS over IPv6 from knfsd (the kernel's NFS server) | |
| 35 | requires that you enable this option and use a portmapper that | |
| 36 | supports rpcbind version 4. | |
| 37 | ||
| 38 | If unsure, say N to get traditional behavior (register kernel | |
| 39 | RPC services using only rpcbind version 2). Distributions | |
| 40 | using the legacy Linux portmapper daemon must say N here. | |
| 41 | ||
| 42 | config RPCSEC_GSS_KRB5 | |
| 43 | tristate "Secure RPC: Kerberos V mechanism (EXPERIMENTAL)" | |
| 44 | depends on SUNRPC && EXPERIMENTAL | |
| 45 | select SUNRPC_GSS | |
| 46 | select CRYPTO | |
| 47 | select CRYPTO_MD5 | |
| 48 | select CRYPTO_DES | |
| 49 | select CRYPTO_CBC | |
| 50 | help | |
| 51 | Choose Y here to enable Secure RPC using the Kerberos version 5 | |
| 52 | GSS-API mechanism (RFC 1964). | |
| 53 | ||
| 54 | Secure RPC calls with Kerberos require an auxiliary user-space | |
| 55 | daemon which may be found in the Linux nfs-utils package | |
| 56 | available from http://linux-nfs.org/. In addition, user-space | |
| 57 | Kerberos support should be installed. | |
| 58 | ||
| 59 | If unsure, say N. | |
| 60 | ||
| 61 | config RPCSEC_GSS_SPKM3 | |
| 62 | tristate "Secure RPC: SPKM3 mechanism (EXPERIMENTAL)" | |
| 63 | depends on SUNRPC && EXPERIMENTAL | |
| 64 | select SUNRPC_GSS | |
| 65 | select CRYPTO | |
| 66 | select CRYPTO_MD5 | |
| 67 | select CRYPTO_DES | |
| 68 | select CRYPTO_CAST5 | |
| 69 | select CRYPTO_CBC | |
| 70 | help | |
| 71 | Choose Y here to enable Secure RPC using the SPKM3 public key | |
| 72 | GSS-API mechansim (RFC 2025). | |
| 73 | ||
| 74 | Secure RPC calls with SPKM3 require an auxiliary userspace | |
| 75 | daemon which may be found in the Linux nfs-utils package | |
| 76 | available from http://linux-nfs.org/. | |
| 77 | ||
| 78 | If unsure, say N. |