Trond, On 2/3/20 10:15 AM, Olga Kornievskaia wrote: > Looks good but can we add clarification that nconnect is supported for > 3.0 and 4.1+? Do you have an opinion on this? Should we document the protocols that are supported? steved. > > On Wed, Jan 29, 2020 at 10:47 AM Steve Dickson <steved@xxxxxxxxxx> wrote: >> >> From: Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> >> >> Add a description of the 'nconnect' mount option on the 'nfs' generic >> manpage. >> >> Signed-off-by: Trond Myklebust <trond.myklebust@xxxxxxxxxxxxxxx> >> Signed-off-by: Steve Dickson <steved@xxxxxxxxxx> >> --- >> utils/mount/nfs.man | 17 +++++++++++++++++ >> 1 file changed, 17 insertions(+) >> >> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man >> index 6ba9cef..84462cd 100644 >> --- a/utils/mount/nfs.man >> +++ b/utils/mount/nfs.man >> @@ -369,6 +369,23 @@ using an automounter (refer to >> .BR automount (8) >> for details). >> .TP 1.5i >> +.BR nconnect= n >> +When using a connection oriented protocol such as TCP, it may >> +sometimes be advantageous to set up multiple connections between >> +the client and server. For instance, if your clients and/or servers >> +are equipped with multiple network interface cards (NICs), using multiple >> +connections to spread the load may improve overall performance. >> +In such cases, the >> +.BR nconnect >> +option allows the user to specify the number of connections >> +that should be established between the client and server up to >> +a limit of 16. >> +.IP >> +Note that the >> +.BR nconnect >> +option may also be used by some pNFS drivers to decide how many >> +connections to set up to the data servers. >> +.TP 1.5i >> .BR rdirplus " / " nordirplus >> Selects whether to use NFS v3 or v4 READDIRPLUS requests. >> If this option is not specified, the NFS client uses READDIRPLUS requests >> -- >> 2.21.1 >> >
