| 1 | config SUNRPC |
| 2 | tristate |
| 3 | depends on MULTIUSER |
| 4 | |
| 5 | config SUNRPC_GSS |
| 6 | tristate |
| 7 | select OID_REGISTRY |
| 8 | depends on MULTIUSER |
| 9 | |
| 10 | config SUNRPC_BACKCHANNEL |
| 11 | bool |
| 12 | depends on SUNRPC |
| 13 | |
| 14 | config SUNRPC_SWAP |
| 15 | bool |
| 16 | depends on SUNRPC |
| 17 | |
| 18 | config RPCSEC_GSS_KRB5 |
| 19 | tristate "Secure RPC: Kerberos V mechanism" |
| 20 | depends on SUNRPC && CRYPTO |
| 21 | depends on CRYPTO_MD5 && CRYPTO_DES && CRYPTO_CBC && CRYPTO_CTS |
| 22 | depends on CRYPTO_ECB && CRYPTO_HMAC && CRYPTO_SHA1 && CRYPTO_AES |
| 23 | depends on CRYPTO_ARC4 |
| 24 | default y |
| 25 | select SUNRPC_GSS |
| 26 | help |
| 27 | Choose Y here to enable Secure RPC using the Kerberos version 5 |
| 28 | GSS-API mechanism (RFC 1964). |
| 29 | |
| 30 | Secure RPC calls with Kerberos require an auxiliary user-space |
| 31 | daemon which may be found in the Linux nfs-utils package |
| 32 | available from http://linux-nfs.org/. In addition, user-space |
| 33 | Kerberos support should be installed. |
| 34 | |
| 35 | If unsure, say Y. |
| 36 | |
| 37 | config SUNRPC_DEBUG |
| 38 | bool "RPC: Enable dprintk debugging" |
| 39 | depends on SUNRPC && SYSCTL |
| 40 | select DEBUG_FS |
| 41 | help |
| 42 | This option enables a sysctl-based debugging interface |
| 43 | that is be used by the 'rpcdebug' utility to turn on or off |
| 44 | logging of different aspects of the kernel RPC activity. |
| 45 | |
| 46 | Disabling this option will make your kernel slightly smaller, |
| 47 | but makes troubleshooting NFS issues significantly harder. |
| 48 | |
| 49 | If unsure, say Y. |
| 50 | |
| 51 | config SUNRPC_XPRT_RDMA |
| 52 | tristate "RPC-over-RDMA transport" |
| 53 | depends on SUNRPC && INFINIBAND && INFINIBAND_ADDR_TRANS |
| 54 | default SUNRPC && INFINIBAND |
| 55 | select SG_POOL |
| 56 | help |
| 57 | This option allows the NFS client and server to use RDMA |
| 58 | transports (InfiniBand, iWARP, or RoCE). |
| 59 | |
| 60 | To compile this support as a module, choose M. The module |
| 61 | will be called rpcrdma.ko. |
| 62 | |
| 63 | If unsure, or you know there is no RDMA capability on your |
| 64 | hardware platform, say N. |