NFS: Update help text for CONFIG_NFS_FS
Subsystems (3)
PATCH 1/5 NFS: Update help text for CONFIG_NFS_FS
Refresh the help text for Kconfig items related to the NFS client. Remove obsolete URLs, and make the language consistent among the options.
Also move the ROOT_NFS config option next to the options related to the NFS client.
---
fs/Kconfig | 136 ++++++++++++++++++++++++++++++------------------------------ 1 files changed, 69 insertions(+), 67 deletions(-)
fs/Kconfig +69 -67
@@ -1517,10 +1517,6 @@ config UFS_FS The recently released UFS2 variant (used in FreeBSD 5.x) is READ-ONLY supported. - If you only intend to mount files from some other Unix over the - network using NFS, you don't need the UFS file system support (but - you need NFS file system support obviously). - Note that this option is generally not needed for floppies, since a good portable way to transport files and directories between unixes (and even other operating systems) is given by the tar program ("man
@@ -1560,6 +1556,7 @@ menuconfig NETWORK_FILESYSTEMS Say Y here to get to see options for network filesystems and filesystem-related networking code, such as NFS daemon and RPCSEC security modules. + This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and
@@ -1574,44 +1571,35 @@ config NFS_FS select SUNRPC select NFS_ACL_SUPPORT if NFS_V3_ACL help - If you are connected to some other (usually local) Unix computer - (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing - on that computer (the NFS server) using the Network File Sharing - protocol, say Y. "Mounting files" means that the client can access - the files with usual UNIX commands as if they were sitting on the - client's hard disk. For this to work, the server must run the - programs nfsd and mountd (but does not need to have NFS file system - support enabled in its kernel). NFS is explained in the Network - Administrator's Guide, available from - <http://www.tldp.org/docs.html#guide>, on its man page: "man - nfs", and in the NFS-HOWTO. - - A superior but less widely used alternative to NFS is provided by - the Coda file system; see "Coda file system support" below. + Say Y here if you want to access files residing on other computers + using the internet standard Network File System protocol. To + compile this file system support as a module, choose M here: the + module will be called nfs. - If you say Y here, you should have said Y to TCP/IP networking also. - This option would enlarge your kernel by about 27 KB. + To mount file systems exported by NFS servers, you also need to + install the user space mount.nfs command which can be found in + the Linux nfs-utils package, available from http://linux-nfs.org/. + Information about using the mount command is available in the + mount(8) man page. More detail about the Linux NFS client + implementation is available via the nfs(5) man page. - To compile this file system support as a module, choose M here: the - module will be called nfs. + Below you can select which versions of the NFS protocol are + available in the kernel to mount NFS servers. Support for NFS + version 2 (RFC 1094) is always available when NFS_FS is selected. - If you are configuring a diskless machine which will mount its root - file system over NFS at boot time, say Y here and to "Kernel - level IP autoconfiguration" above and to "Root file system on NFS" - below. You cannot compile this driver as a module in this case. - There are two packages designed for booting diskless machines over - the net: netboot, available from - <http://ftp1.sourceforge.net/netboot/>, and Etherboot, - available from <http://ftp1.sourceforge.net/etherboot/>. + To configure a system which mounts its root file system via NFS at + boot time, say Y here, select "Kernel level IP autoconfiguration" + in the NETWORK menu, and select "Root file system on NFS" below. + You cannot compile this driver as a module in this case. - If you don't know what all this is about, say N. + If unsure, say N. config NFS_V3 bool "Provide NFSv3 client support" depends on NFS_FS help - Say Y here if you want your NFS client to be able to speak version - 3 of the NFS protocol. + This option enables support for version 3 of the NFS protocol + (RFC 1813) in the kernel's NFS client. If unsure, say Y.
@@ -1619,9 +1607,21 @@ config NFS_V3_ACL bool "Provide client support for the NFSv3 ACL protocol extension" depends on NFS_V3 help - Implement the NFSv3 ACL protocol extension for manipulating POSIX - Access Control Lists. The server should also be compiled with - the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option. + Some NFS servers support an auxiliary NFSv3 ACL protocol that + Sun added to Solaris but never became an official part of the + NFS version 3 protocol. This nonstandard side-band protocol + allows applications on NFS clients to manipulate POSIX Access + Control Lists on files residing on NFS servers. NFS servers + enforce ACLs on local files whether this protocol is available + or not. + + Say Y here if your NFS server supports the Solaris NFSv3 ACL + protocol and you want your NFS client to allow applications to + access and modify ACLs on files on the server. + + Some NFS servers don't support the Solaris NFSv3 ACL protocol. + You can say N here or specify the "noacl" mount option to prevent + your NFS client from trying to use the NFSv3 ACL protocol. If unsure, say N.
@@ -1630,38 +1630,54 @@ config NFS_V4 depends on NFS_FS && EXPERIMENTAL select RPCSEC_GSS_KRB5 help - Say Y here if you want your NFS client to be able to speak the newer - version 4 of the NFS protocol. + This option enables support for version 4 of the NFS protocol + (RFC 3530) in the kernel's NFS client. - Note: Requires auxiliary userspace daemons which may be found on - http://www.citi.umich.edu/projects/nfsv4/ + To mount NFS servers using NFSv4, you also need to install user + space programs which can be found in the Linux nfs-utils package, + available from http://linux-nfs.org/. If unsure, say N. config NFS_DIRECTIO bool "Allow direct I/O on NFS files" depends on NFS_FS + default N help - This option enables applications to perform uncached I/O on files - in NFS file systems using the O_DIRECT open() flag. When O_DIRECT - is set for a file, its data is not cached in the system's page - cache. Data is moved to and from user-level application buffers - directly. Unlike local disk-based file systems, NFS O_DIRECT has - no alignment restrictions. + This option enables support for uncached I/O on files accessed + via an NFS mount point. Applications request direct I/O by + setting the O_DIRECT flag when opening a file. + + When direct I/O is requested, the NFS client moves data to and + from user-level application buffers directly to NFS servers. + Direct I/O on NFS files does not suffer from any I/O or buffer + alignment restrictions, as does direct I/O on files that reside + in local file systems. + + For details, see the open(2) man page. Unless your program is designed to use O_DIRECT properly, you are - much better off allowing the NFS client to manage data caching for - you. Misusing O_DIRECT can cause poor server performance or network - storms. This kernel build option defaults OFF to avoid exposing + better off allowing the NFS client to manage data caching for you. + Misusing O_DIRECT can cause poor server performance or network + storms. This kernel build option defaults to N to avoid exposing system administrators unwittingly to a potentially hazardous feature. - For more details on NFS O_DIRECT, see fs/nfs/direct.c. - - If unsure, say N. This reduces the size of the NFS client, and - causes open() to return EINVAL if a file residing in NFS is + If unsure, say N. This reduces the size of the kernel NFS client, + and causes open(2) to return EINVAL if a file residing in NFS is opened with the O_DIRECT flag. +config ROOT_NFS + bool "Root file system on NFS" + depends on NFS_FS=y && IP_PNP + help + If you want your system to mount its root file system via NFS, say + Y here. This is common practice for managing systems without + local permanent storage. Read <file:Documentation/nfsroot.txt> + for details. + + Most people say N here. + config NFSD tristate "NFS server support" depends on INET
@@ -1738,20 +1754,6 @@ config NFSD_TCP TCP connections usually perform better than the default UDP when the network is lossy or congested. If unsure, say Y. -config ROOT_NFS - bool "Root file system on NFS" - depends on NFS_FS=y && IP_PNP - help - If you want your Linux box to mount its whole root file system (the - one containing the directory /) from some other computer over the - net via NFS (presumably because your box doesn't have a hard disk), - say Y. Read <file:Documentation/nfsroot.txt> for details. It is - likely that in this case, you also want to say Y to "Kernel level IP - autoconfiguration" so that your box can discover its network address - at boot time. - - Most people say N here. - config LOCKD tristate
A message that is not in the archive (sent off-list or not yet received): 20080205000421.18602.44285.stgit-meopP2rzCrTwdl/1UfZZQIVfYA8g3rJ/@public.gmane.org
Quoted 45 lines · Chuck Lever
Refresh the help text for
Kconfigitems related to the NFS client. Remove obsolete URLs, and make the language consistent among the options.Also move the
ROOT_NFSconfig option next to the options related to the NFS client.Signed-off-by Chuck Lever <[email protected]>---
fs/Kconfig | 136 ++++++++++++++++++++++++++++++------------------------------ 1 files changed, 69 insertions(+), 67 deletions(-)fs/Kconfig +1
-10@@ -1517,10 +1517,6 @@ config UFS_FS The recently released UFS2 variant (used in FreeBSD 5.x) is READ-ONLY supported. - If you only intend to mount files from some other Unix over the - network using NFS, you don't need the UFS file system support (but - you need NFS file system support obviously). - Note that this option is generally not needed for floppies, since a good portable way to transport files and directories between unixes (and even other operating systems) is given by the tar program ("man@@ -1560,6 +1556,7 @@ menuconfig NETWORK_FILESYSTEMS Say Y here to get to see options for network filesystems and filesystem-related networking code, such as NFS daemon and RPCSEC security modules. + This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and@@ -1574,44 +1571,35 @@ config NFS_FS select SUNRPC select NFS_ACL_SUPPORT if NFS_V3_ACL help - If you are connected to some other (usually local) Unix computer - (using SLIP, PLIP, PPP or Ethernet) and want to mount files residing - on that computer (the NFS server) using the Network File Sharing - protocol, say Y. "Mounting files" means that the client can access - the files with usual UNIX commands as if they were sitting on the - client's hard disk. For this to work, the server must run the
fs/Kconfig config NFS_FS · line 1575
Quoted 10 lines
fs/Kconfig +2
-8- programs nfsd and mountd (but does not need to have NFS file system - support enabled in its kernel). NFS is explained in the Network - Administrator's Guide, available from - <http://www.tldp.org/docs.html#guide>, on its man page: "man - nfs", and in the NFS-HOWTO. - - A superior but less widely used alternative to NFS is provided by - the Coda file system; see "Coda file system support" below. + Say Y here if you want to access files residing on other computers + using the internet standard Network File System protocol. To
Tsk, tsk.... NFS isn't an internet standard (yet!).
Quoted 55 lines
fs/Kconfig +21
-18+ compile this file system support as a module, choose M here: the + module will be called nfs. - If you say Y here, you should have said Y to TCP/IP networking also. - This option would enlarge your kernel by about 27 KB. + To mount file systems exported by NFS servers, you also need to + install the user space mount.nfs command which can be found in + the Linux nfs-utils package, available from http://linux-nfs.org/. + Information about using the mount command is available in the + mount(8) man page. More detail about the Linux NFS client + implementation is available via the nfs(5) man page. - To compile this file system support as a module, choose M here: the - module will be called nfs. + Below you can select which versions of the NFS protocol are + available in the kernel to mount NFS servers. Support for NFS + version 2 (RFC 1094) is always available when NFS_FS is selected. - If you are configuring a diskless machine which will mount its root - file system over NFS at boot time, say Y here and to "Kernel - level IP autoconfiguration" above and to "Root file system on NFS" - below. You cannot compile this driver as a module in this case. - There are two packages designed for booting diskless machines over - the net: netboot, available from - <http://ftp1.sourceforge.net/netboot/>, and Etherboot, - available from <http://ftp1.sourceforge.net/etherboot/>. + To configure a system which mounts its root file system via NFS at + boot time, say Y here, select "Kernel level IP autoconfiguration" + in the NETWORK menu, and select "Root file system on NFS" below. + You cannot compile this driver as a module in this case. - If you don't know what all this is about, say N. + If unsure, say N. config NFS_V3 bool "Provide NFSv3 client support" depends on NFS_FS help - Say Y here if you want your NFS client to be able to speak version - 3 of the NFS protocol. + This option enables support for version 3 of the NFS protocol + (RFC 1813) in the kernel's NFS client. If unsure, say Y.@@ -1619,9 +1607,21 @@ config NFS_V3_ACL bool "Provide client support for the NFSv3 ACL protocol extension" depends on NFS_V3 help - Implement the NFSv3 ACL protocol extension for manipulating POSIX - Access Control Lists. The server should also be compiled with - the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACL option. + Some NFS servers support an auxiliary NFSv3 ACL protocol that + Sun added to Solaris but never became an official part of the + NFS version 3 protocol. This nonstandard side-band protocol
fs/Kconfig config NFS_V3_ACL · line 1622
Quoted 10 lines
fs/Kconfig +10
-0+ allows applications on NFS clients to manipulate POSIX Access + Control Lists on files residing on NFS servers. NFS servers + enforce ACLs on local files whether this protocol is available + or not. + + Say Y here if your NFS server supports the Solaris NFSv3 ACL + protocol and you want your NFS client to allow applications to + access and modify ACLs on files on the server. + + Some NFS servers don't support the Solaris NFSv3 ACL protocol.
^^^^ Most?
Quoted 16 lines
fs/Kconfig +4
-4+ You can say N here or specify the "noacl" mount option to prevent + your NFS client from trying to use the NFSv3 ACL protocol. If unsure, say N.@@ -1630,38 +1630,54 @@ config NFS_V4 depends on NFS_FS && EXPERIMENTAL select RPCSEC_GSS_KRB5 help - Say Y here if you want your NFS client to be able to speak the newer - version 4 of the NFS protocol. + This option enables support for version 4 of the NFS protocol + (RFC 3530) in the kernel's NFS client. - Note: Requires auxiliary userspace daemons which may be found on - http://www.citi.umich.edu/projects/nfsv4/
fs/Kconfig config NFS_V4 · line 1645
Quoted 10 lines
fs/Kconfig +4
-0+ To mount NFS servers using NFSv4, you also need to install user + space programs which can be found in the Linux nfs-utils package, + available from http://linux-nfs.org/. If unsure, say N. config NFS_DIRECTIO bool "Allow direct I/O on NFS files" depends on NFS_FS + default N
Why? Isn't O_DIRECT pretty much a standard feature that is enabled in most distros at this time?
IMO we should rather be aiming to phase out NFS_DIRECTIO.
Quoted 77 lines
fs/Kconfig +27
-28help - This option enables applications to perform uncached I/O on files - in NFS file systems using the O_DIRECT open() flag. When O_DIRECT - is set for a file, its data is not cached in the system's page - cache. Data is moved to and from user-level application buffers - directly. Unlike local disk-based file systems, NFS O_DIRECT has - no alignment restrictions. + This option enables support for uncached I/O on files accessed + via an NFS mount point. Applications request direct I/O by + setting the O_DIRECT flag when opening a file. + + When direct I/O is requested, the NFS client moves data to and + from user-level application buffers directly to NFS servers. + Direct I/O on NFS files does not suffer from any I/O or buffer + alignment restrictions, as does direct I/O on files that reside + in local file systems. + + For details, see the open(2) man page. Unless your program is designed to use O_DIRECT properly, you are - much better off allowing the NFS client to manage data caching for - you. Misusing O_DIRECT can cause poor server performance or network - storms. This kernel build option defaults OFF to avoid exposing + better off allowing the NFS client to manage data caching for you. + Misusing O_DIRECT can cause poor server performance or network + storms. This kernel build option defaults to N to avoid exposing system administrators unwittingly to a potentially hazardous feature. - For more details on NFS O_DIRECT, see fs/nfs/direct.c. - - If unsure, say N. This reduces the size of the NFS client, and - causes open() to return EINVAL if a file residing in NFS is + If unsure, say N. This reduces the size of the kernel NFS client, + and causes open(2) to return EINVAL if a file residing in NFS is opened with the O_DIRECT flag. +config ROOT_NFS + bool "Root file system on NFS" + depends on NFS_FS=y && IP_PNP + help + If you want your system to mount its root file system via NFS, say + Y here. This is common practice for managing systems without + local permanent storage. Read <file:Documentation/nfsroot.txt> + for details. + + Most people say N here. + config NFSD tristate "NFS server support" depends on INET@@ -1738,20 +1754,6 @@ config NFSD_TCP TCP connections usually perform better than the default UDP when the network is lossy or congested. If unsure, say Y. -config ROOT_NFS - bool "Root file system on NFS" - depends on NFS_FS=y && IP_PNP - help - If you want your Linux box to mount its whole root file system (the - one containing the directory /) from some other computer over the - net via NFS (presumably because your box doesn't have a hard disk), - say Y. Read <file:Documentation/nfsroot.txt> for details. It is - likely that in this case, you also want to say Y to "Kernel level IP - autoconfiguration" so that your box can discover its network address - at boot time. - - Most people say N here. - config LOCKD tristate -To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
A message that is not in the archive (sent off-list or not yet received): 1202170682.28484.55.camel-rJ7iovZKK19ZJLDQqaL3InhyD016LWXt@public.gmane.org
Quoted 6 lines · Trond Myklebust
Quoted 4 lines · Chuck Lever
Refresh the help text for
Kconfigitems related to the NFS client. Remove obsolete URLs, and make the language consistent among the options.
Quoted 10 lines
fs/Kconfig config NFS_V4 · line 1645
Quoted 5 lines
config
NFS_DIRECTIOfs/Kconfig +1
-0bool "Allow direct I/O on NFS files" depends on NFS_FS + default NWhy? Isn't
O_DIRECTpretty much a standard feature that is enabled in most distros at this time?
IMO we should rather be aiming to phase outNFS_DIRECTIO.
Agreed.
Quoted 10 lines
Quoted 10 lines
fs/Kconfig +2
-6help - This option enables applications to perform uncached I/O on files - in NFS file systems using the O_DIRECT open() flag. When O_DIRECT - is set for a file, its data is not cached in the system's page - cache. Data is moved to and from user-level application buffers - directly. Unlike local disk-based file systems, NFS O_DIRECT has - no alignment restrictions. + This option enables support for uncached I/O on files accessed + via an NFS mount point. Applications request direct I/O by
Quoted 8 lines
fs/Kconfig config NFS_V4 · line 1655
Quoted 8 lines
fs/Kconfig +7
-0+ setting the O_DIRECT flag when opening a file. + + When direct I/O is requested, the NFS client moves data to and + from user-level application buffers directly to NFS servers. + Direct I/O on NFS files does not suffer from any I/O or buffer + alignment restrictions, as does direct I/O on files that reside + in local file systems.
It might be an idea to mention that direct IO does *not* bypass the server's page cache, an unobvious semantic which escapes many people.
Quoted 3 lines
Review
Quoted 3 lines
(quoted diff) +2
-0+ + For details, see the open(2) man page.
FYI, I recently posted an update to the O_DIRECT documentation in open(2).
http://marc.info/?l=linux-man&m=120107005026531&w=2
Signature · 3 lines
Greg Banks, R&D Software Engineer, SGI Australian Software Group. The cake is *not* a lie. I don't speak for SGI.
Quoted 60 lines · Trond Myklebust
Quoted 59 lines · Chuck Lever
Refresh the help text for
Kconfigitems related to the NFS client. Remove obsolete URLs, and make the language consistent among the options.Also move the
ROOT_NFSconfig option next to the options related to the NFS client.Signed-off-by Chuck Lever <[email protected]>---
fs/Kconfig | 136 +++++++++++++++++++++++++++++ +------------------------------ 1 files changed, 69 insertions(+), 67 deletions(-)fs/Kconfig +0
-0@@ -1517,10 +1517,6 @@ config UFS_FS The recently released UFS2 variant (used in FreeBSD5.x) is
READ-ONLY supported.fs/Kconfig +0
-2- If you only intend to mount files from some other Unix over the - network using NFS, you don't need the UFS file system support(but
fs/Kconfig +0
-2- you need NFS file system support obviously). - Note that this option is generally not needed for floppies,since a
good portable way to transport files and directories between
unixes
(and even other operating systems) is given by the tar program
("manfs/Kconfig +1
-2@@ -1560,6 +1556,7 @@ menuconfig NETWORK_FILESYSTEMS Say Y here to get to see options for network filesystems and filesystem-related networking code, such as NFS daemon and RPCSEC security modules. + This option alone does not add any kernel code. If you say N, all options in this submenu will be skipped and@@ -1574,44 +1571,35 @@ config NFS_FS select SUNRPC select NFS_ACL_SUPPORT if NFS_V3_ACL help - If you are connected to some other (usually local) Unix computer - (using SLIP, PLIP, PPP or Ethernet) and want to mount filesresiding
fs/Kconfig +0
-2- on that computer (the NFS server) using the Network File Sharing - protocol, say Y. "Mounting files" means that the client canaccess
fs/Kconfig +0
-3- the files with usual UNIX commands as if they were sitting on the - client's hard disk. For this to work, the server must run the - programs nfsd and mountd (but does not need to have NFS filesystem
fs/Kconfig +0
-4- support enabled in its kernel). NFS is explained in the Network - Administrator's Guide, available from - <http://www.tldp.org/docs.html#guide>, on its man page: "man - nfs", and in the NFS-HOWTO.
Quoted 8 lines
fs/Kconfig config NFS_FS · line 1575
Quoted 6 lines
fs/Kconfig +1
-3- - A superior but less widely used alternative to NFS is provided by - the Coda file system; see "Coda file system support" below. + Say Y here if you want to access files residing on othercomputers
fs/Kconfig +1
-0+ using the internet standard Network File System protocol. ToTsk, tsk.... NFS isn't an internet standard (yet!).
Well, I used lower case. :-)
How about "proposed internet standard" or "de-facto internet standard" ? We could say "Sun Network File System" but that's just so antique.
Quoted 67 lines
Quoted 67 lines
fs/Kconfig +2
-1+ compile this file system support as a module, choose M here: the + module will be called nfs. - If you say Y here, you should have said Y to TCP/IP networkingalso.
fs/Kconfig +3
-1- This option would enlarge your kernel by about 27 KB. + To mount file systems exported by NFS servers, you also need to + install the user space mount.nfs command which can be found in + the Linux nfs-utils package, available from http://linux-nfs.org/.
fs/Kconfig +3
-1+ Information about using the mount command is available in the + mount(8) man page. More detail about the Linux NFS client + implementation is available via the nfs(5) man page. - To compile this file system support as a module, choose Mhere: the
fs/Kconfig +3
-2- module will be called nfs. + Below you can select which versions of the NFS protocol are + available in the kernel to mount NFS servers. Support for NFS + version 2 (RFC 1094) is always available when NFS_FS is selected. - If you are configuring a diskless machine which will mount itsroot
fs/Kconfig +0
-2- file system over NFS at boot time, say Y here and to "Kernel - level IP autoconfiguration" above and to "Root file system onNFS"
fs/Kconfig +0
-2- below. You cannot compile this driver as a module in this case. - There are two packages designed for booting diskless machinesover
fs/Kconfig +1
-3- the net: netboot, available from - <http://ftp1.sourceforge.net/netboot/>, and Etherboot, - available from <http://ftp1.sourceforge.net/etherboot/>. + To configure a system which mounts its root file system viaNFS at
fs/Kconfig +4
-2+ boot time, say Y here, select "Kernel level IP autoconfiguration" + in the NETWORK menu, and select "Root file system on NFS" below. + You cannot compile this driver as a module in this case. - If you don't know what all this is about, say N. + If unsure, say N. config NFS_V3 bool "Provide NFSv3 client support" depends on NFS_FS help - Say Y here if you want your NFS client to be able to speakversion
fs/Kconfig +2
-4- 3 of the NFS protocol. + This option enables support for version 3 of the NFS protocol + (RFC 1813) in the kernel's NFS client. If unsure, say Y.@@ -1619,9 +1607,21 @@ config NFS_V3_ACL bool "Provide client support for the NFSv3 ACL protocol extension" depends on NFS_V3 help - Implement the NFSv3 ACL protocol extension for manipulating POSIX - Access Control Lists. The server should also be compiled with - the NFSv3 ACL protocol extension; see the CONFIG_NFSD_V3_ACLoption.
fs/Kconfig +6
-0+ Some NFS servers support an auxiliary NFSv3 ACL protocol that + Sun added to Solaris but never became an official part of the + NFS version 3 protocol. This nonstandard side-band protocol + allows applications on NFS clients to manipulate POSIX Access + Control Lists on files residing on NFS servers. NFS servers + enforce ACLs on local files whether this protocol is available
Quoted 8 lines
fs/Kconfig config NFS_V3_ACL · line 1622
Quoted 7 lines
fs/Kconfig +7
-0+ or not. + + Say Y here if your NFS server supports the Solaris NFSv3 ACL + protocol and you want your NFS client to allow applications to + access and modify ACLs on files on the server. + + Some NFS servers don't support the Solaris NFSv3 ACL protocol.^^^^ Most?
Fixed.
Quoted 23 lines
Quoted 23 lines
fs/Kconfig +2
-1+ You can say N here or specify the "noacl" mount option to prevent + your NFS client from trying to use the NFSv3 ACL protocol. If unsure, say N.@@ -1630,38 +1630,54 @@ config NFS_V4 depends on NFS_FS && EXPERIMENTAL select RPCSEC_GSS_KRB5 help - Say Y here if you want your NFS client to be able to speak thenewer
fs/Kconfig +5
-3- version 4 of the NFS protocol. + This option enables support for version 4 of the NFS protocol + (RFC 3530) in the kernel's NFS client. - Note: Requires auxiliary userspace daemons which may be found on - http://www.citi.umich.edu/projects/nfsv4/ + To mount NFS servers using NFSv4, you also need to install user + space programs which can be found in the Linux nfs-utils package, + available from http://linux-nfs.org/. If unsure, say N.
Quoted 8 lines
fs/Kconfig config NFS_V4 · line 1645
Quoted 4 lines
config
NFS_DIRECTIOfs/Kconfig +1
-0bool "Allow direct I/O on NFS files" depends on NFS_FS + default NWhy? Isn't
O_DIRECTpretty much a standard feature that is enabled in most distros at this time?
IMO we should rather be aiming to phase outNFS_DIRECTIO.
Using a build option that defaults "off" was your idea, all these many years ago, as was the language in the help text about how dangerous uncached I/O is.
I would be happy to provide a patch for 2.6.25 that simply excises CONFIG_NFS_DIRECTIO and leaves the NFS direct I/O engine always built in.
Quoted 73 lines
Quoted 73 lines
fs/Kconfig +0
-2help - This option enables applications to perform uncached I/O on files - in NFS file systems using the O_DIRECT open() flag. When
O_DIRECTfs/Kconfig +11
-5- is set for a file, its data is not cached in the system's page - cache. Data is moved to and from user-level application buffers - directly. Unlike local disk-based file systems, NFS O_DIRECT has - no alignment restrictions. + This option enables support for uncached I/O on files accessed + via an NFS mount point. Applications request direct I/O by + setting the O_DIRECT flag when opening a file. + + When direct I/O is requested, the NFS client moves data to and + from user-level application buffers directly to NFS servers. + Direct I/O on NFS files does not suffer from any I/O or buffer + alignment restrictions, as does direct I/O on files that reside + in local file systems. + + For details, see the open(2) man page. Unless your program is designed to use O_DIRECT properly, you are - much better off allowing the NFS client to manage data cachingfor
fs/Kconfig +0
-1- you. Misusing O_DIRECT can cause poor server performance ornetwork
fs/Kconfig +1
-1- storms. This kernel build option defaults OFF to avoid exposing + better off allowing the NFS client to manage data caching foryou.
fs/Kconfig +3
-4+ Misusing O_DIRECT can cause poor server performance or network + storms. This kernel build option defaults to N to avoid exposing system administrators unwittingly to a potentially hazardous feature. - For more details on NFS O_DIRECT, see fs/nfs/direct.c. - - If unsure, say N. This reduces the size of the NFS client, and - causes open() to return EINVAL if a file residing in NFS is + If unsure, say N. This reduces the size of the kernel NFSclient,
fs/Kconfig +6
-0+ and causes open(2) to return EINVAL if a file residing in NFS is opened with the O_DIRECT flag. +config ROOT_NFS + bool "Root file system on NFS" + depends on NFS_FS=y && IP_PNP + help + If you want your system to mount its root file system via NFS,say
fs/Kconfig +6
-5+ Y here. This is common practice for managing systems without + local permanent storage. Read <file:Documentation/nfsroot.txt> + for details. + + Most people say N here. + config NFSD tristate "NFS server support" depends on INET@@ -1738,20 +1754,6 @@ config NFSD_TCP TCP connections usually perform better than the default UDP when the network is lossy or congested. If unsure, say Y. -config ROOT_NFS - bool "Root file system on NFS" - depends on NFS_FS=y && IP_PNP - help - If you want your Linux box to mount its whole root file system(the
fs/Kconfig +0
-2- one containing the directory /) from some other computer over the - net via NFS (presumably because your box doesn't have a harddisk),
fs/Kconfig +0
-2- say Y. Read <file:Documentation/nfsroot.txt> for details. It is - likely that in this case, you also want to say Y to "Kernellevel IP
Quoted 8 lines
fs/Kconfig config NFSD_TCP · line 1758
Quoted 8 lines
fs/Kconfig +0
-1- autoconfiguration" so that your box can discover its networkaddress
fs/Kconfig +0
-4- at boot time. - - Most people say N here. - config LOCKD tristate
--
Chuck Lever
chuck[dot]lever[at]oracle[dot]com