On 8/27/21 2:37 PM, Olga Kornievskaia wrote:
From: Olga Kornievskaia <kolga@xxxxxxxxxx> When client discovers trunkable servers, instead of dropping newly created trunkable connections, add this connection to the existing RPC client. Signed-off-by: Olga Kornievskaia <kolga@xxxxxxxxxx>
Committed.... (tag: nfs-utils-2-5-5-rc3) steved.
--- utils/mount/nfs.man | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man index f1b76936..57a693fd 100644 --- a/utils/mount/nfs.man +++ b/utils/mount/nfs.man @@ -416,6 +416,19 @@ Note that the 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 max_connect= n +While +.BR nconnect +option sets a limit on the number of connections that can be established +to a given server IP, +.BR max_connect +option allows the user to specify maximum number of connections to different +server IPs that belong to the same NFSv4.1+ server (session trunkable +connections) up to a limit of 16. When client discovers that it established +a client ID to an already existing server, instead of dropping the newly +created network transport, the client will add this new connection to the +list of available transports for that RPC client. +.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
