CONFIG_NFSD_LOCALIO controls the server enablement for localio. An earlier commit added CONFIG_NFS_LOCALIO to allow the client enablement. While it is true that it doesn't make sense, on a using LOCALIO level, to have one without the other: it is useful to allow a mix be configured for testing purposes. It could be that the same control could be achieved by exposing a discrete "localio_enabled" module_param in the server (nfsd.ko) like is already available in the client (nfs.ko). Signed-off-by: Mike Snitzer <snitzer@xxxxxxxxxx> --- fs/nfsd/Kconfig | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/fs/nfsd/Kconfig b/fs/nfsd/Kconfig index ec2ab6429e00..a36ff66c7430 100644 --- a/fs/nfsd/Kconfig +++ b/fs/nfsd/Kconfig @@ -89,6 +89,20 @@ config NFSD_V4 If unsure, say N. +config NFSD_LOCALIO + tristate "NFS server support for the LOCALIO auxiliary protocol" + depends on NFSD || NFSD_V4 + select NFS_COMMON_LOCALIO_SUPPORT + help + Some NFS servers support an auxiliary NFS LOCALIO protocol + that is not an official part of the NFS version 3 or 4 protocol. + + This option enables support for the LOCALIO protocol in the + kernel's NFS server. Enable this to bypass using the NFS + protocol when issuing reads, writes and commits to the server. + + If unsure, say N. + config NFSD_PNFS bool -- 2.44.0
