From: Olga Kornievskaia <olga.kornievskaia@gmail.com>
To: trond.myklebust@hammerspace.com, anna.schumaker@netapp.com,
steved@redhat.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH] [man]: adding new mount option max_connect
Date: Fri, 27 Aug 2021 14:37:15 -0400 [thread overview]
Message-ID: <20210827183719.41057-3-olga.kornievskaia@gmail.com> (raw)
In-Reply-To: <20210827183719.41057-1-olga.kornievskaia@gmail.com>
From: Olga Kornievskaia <kolga@netapp.com>
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@netapp.com>
---
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
--
2.27.0
next prev parent reply other threads:[~2021-08-27 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-27 18:37 [PATCH v5 0/5] do not collapse trunkable transports Olga Kornievskaia
2021-08-27 18:37 ` [PATCH v5 1/5] SUNRPC keep track of number of transports to unique addresses Olga Kornievskaia
2021-08-27 18:37 ` Olga Kornievskaia [this message]
2021-09-23 16:35 ` [PATCH] [man]: adding new mount option max_connect Steve Dickson
2021-08-27 18:37 ` [PATCH v5 2/5] SUNRPC add xps_nunique_destaddr_xprts to xprt_switch_info in sysfs Olga Kornievskaia
2021-08-27 18:37 ` [PATCH v5 3/5] NFSv4 introduce max_connect mount options Olga Kornievskaia
2021-08-27 18:37 ` [PATCH v5 4/5] SUNRPC enforce creation of no more than max_connect xprts Olga Kornievskaia
2021-08-27 18:37 ` [PATCH v5 5/5] NFSv4.1 add network transport when session trunking is detected Olga Kornievskaia
-- strict thread matches above, loose matches on Subject: below --
2021-08-24 17:51 [PATCH v4 0/5] do not collapse trunkable transports Olga Kornievskaia
2021-08-24 17:51 ` [PATCH] [man]: adding new mount option max_connect Olga Kornievskaia
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210827183719.41057-3-olga.kornievskaia@gmail.com \
--to=olga.kornievskaia@gmail.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=steved@redhat.com \
--cc=trond.myklebust@hammerspace.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).