diff options
Diffstat (limited to 'fs/Kconfig')
-rw-r--r-- | fs/Kconfig | 70 |
1 files changed, 33 insertions, 37 deletions
diff --git a/fs/Kconfig b/fs/Kconfig index 56c83f40cdbe..2e43d46f65d6 100644 --- a/fs/Kconfig +++ b/fs/Kconfig | |||
@@ -1664,30 +1664,6 @@ config NFS_V4 | |||
1664 | 1664 | ||
1665 | If unsure, say N. | 1665 | If unsure, say N. |
1666 | 1666 | ||
1667 | config NFS_DIRECTIO | ||
1668 | bool "Allow direct I/O on NFS files" | ||
1669 | depends on NFS_FS | ||
1670 | help | ||
1671 | This option enables applications to perform uncached I/O on files | ||
1672 | in NFS file systems using the O_DIRECT open() flag. When O_DIRECT | ||
1673 | is set for a file, its data is not cached in the system's page | ||
1674 | cache. Data is moved to and from user-level application buffers | ||
1675 | directly. Unlike local disk-based file systems, NFS O_DIRECT has | ||
1676 | no alignment restrictions. | ||
1677 | |||
1678 | Unless your program is designed to use O_DIRECT properly, you are | ||
1679 | much better off allowing the NFS client to manage data caching for | ||
1680 | you. Misusing O_DIRECT can cause poor server performance or network | ||
1681 | storms. This kernel build option defaults OFF to avoid exposing | ||
1682 | system administrators unwittingly to a potentially hazardous | ||
1683 | feature. | ||
1684 | |||
1685 | For more details on NFS O_DIRECT, see fs/nfs/direct.c. | ||
1686 | |||
1687 | If unsure, say N. This reduces the size of the NFS client, and | ||
1688 | causes open() to return EINVAL if a file residing in NFS is | ||
1689 | opened with the O_DIRECT flag. | ||
1690 | |||
1691 | config NFSD | 1667 | config NFSD |
1692 | tristate "NFS server support" | 1668 | tristate "NFS server support" |
1693 | depends on INET | 1669 | depends on INET |
@@ -1813,15 +1789,33 @@ config SUNRPC_XPRT_RDMA | |||
1813 | tristate | 1789 | tristate |
1814 | depends on SUNRPC && INFINIBAND && EXPERIMENTAL | 1790 | depends on SUNRPC && INFINIBAND && EXPERIMENTAL |
1815 | default SUNRPC && INFINIBAND | 1791 | default SUNRPC && INFINIBAND |
1792 | help | ||
1793 | This option enables an RPC client transport capability that | ||
1794 | allows the NFS client to mount servers via an RDMA-enabled | ||
1795 | transport. | ||
1796 | |||
1797 | To compile RPC client RDMA transport support as a module, | ||
1798 | choose M here: the module will be called xprtrdma. | ||
1799 | |||
1800 | If unsure, say N. | ||
1816 | 1801 | ||
1817 | config SUNRPC_BIND34 | 1802 | config SUNRPC_BIND34 |
1818 | bool "Support for rpcbind versions 3 & 4 (EXPERIMENTAL)" | 1803 | bool "Support for rpcbind versions 3 & 4 (EXPERIMENTAL)" |
1819 | depends on SUNRPC && EXPERIMENTAL | 1804 | depends on SUNRPC && EXPERIMENTAL |
1805 | default n | ||
1820 | help | 1806 | help |
1821 | Provides kernel support for querying rpcbind servers via versions 3 | 1807 | RPC requests over IPv6 networks require support for larger |
1822 | and 4 of the rpcbind protocol. The kernel automatically falls back | 1808 | addresses when performing an RPC bind. Sun added support for |
1823 | to version 2 if a remote rpcbind service does not support versions | 1809 | IPv6 addressing by creating two new versions of the rpcbind |
1824 | 3 or 4. | 1810 | protocol (RFC 1833). |
1811 | |||
1812 | This option enables support in the kernel RPC client for | ||
1813 | querying rpcbind servers via versions 3 and 4 of the rpcbind | ||
1814 | protocol. The kernel automatically falls back to version 2 | ||
1815 | if a remote rpcbind service does not support versions 3 or 4. | ||
1816 | By themselves, these new versions do not provide support for | ||
1817 | RPC over IPv6, but the new protocol versions are necessary to | ||
1818 | support it. | ||
1825 | 1819 | ||
1826 | If unsure, say N to get traditional behavior (version 2 rpcbind | 1820 | If unsure, say N to get traditional behavior (version 2 rpcbind |
1827 | requests only). | 1821 | requests only). |
@@ -1835,12 +1829,13 @@ config RPCSEC_GSS_KRB5 | |||
1835 | select CRYPTO_DES | 1829 | select CRYPTO_DES |
1836 | select CRYPTO_CBC | 1830 | select CRYPTO_CBC |
1837 | help | 1831 | help |
1838 | Provides for secure RPC calls by means of a gss-api | 1832 | Choose Y here to enable Secure RPC using the Kerberos version 5 |
1839 | mechanism based on Kerberos V5. This is required for | 1833 | GSS-API mechanism (RFC 1964). |
1840 | NFSv4. | ||
1841 | 1834 | ||
1842 | Note: Requires an auxiliary userspace daemon which may be found on | 1835 | Secure RPC calls with Kerberos require an auxiliary user-space |
1843 | http://www.citi.umich.edu/projects/nfsv4/ | 1836 | daemon which may be found in the Linux nfs-utils package |
1837 | available from http://linux-nfs.org/. In addition, user-space | ||
1838 | Kerberos support should be installed. | ||
1844 | 1839 | ||
1845 | If unsure, say N. | 1840 | If unsure, say N. |
1846 | 1841 | ||
@@ -1854,11 +1849,12 @@ config RPCSEC_GSS_SPKM3 | |||
1854 | select CRYPTO_CAST5 | 1849 | select CRYPTO_CAST5 |
1855 | select CRYPTO_CBC | 1850 | select CRYPTO_CBC |
1856 | help | 1851 | help |
1857 | Provides for secure RPC calls by means of a gss-api | 1852 | Choose Y here to enable Secure RPC using the SPKM3 public key |
1858 | mechanism based on the SPKM3 public-key mechanism. | 1853 | GSS-API mechansim (RFC 2025). |
1859 | 1854 | ||
1860 | Note: Requires an auxiliary userspace daemon which may be found on | 1855 | Secure RPC calls with SPKM3 require an auxiliary userspace |
1861 | http://www.citi.umich.edu/projects/nfsv4/ | 1856 | daemon which may be found in the Linux nfs-utils package |
1857 | available from http://linux-nfs.org/. | ||
1862 | 1858 | ||
1863 | If unsure, say N. | 1859 | If unsure, say N. |
1864 | 1860 | ||