From: Steve Dickson <SteveD@RedHat.com>
To: Linux NFS Mailing list <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/2] manpage: Add a description of the 'nconnect' mount option
Date: Fri, 7 Feb 2020 11:08:35 -0500 [thread overview]
Message-ID: <d1a3745e-cda0-d84c-3cff-47d23df105cb@RedHat.com> (raw)
In-Reply-To: <20200129154703.6204-1-steved@redhat.com>
On 1/29/20 10:47 AM, Steve Dickson wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> Add a description of the 'nconnect' mount option on the 'nfs' generic
> manpage.
>
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> Signed-off-by: Steve Dickson <steved@redhat.com>
Committed... (tag: nfs-utils-2-4-3-rc7)
steved.
> ---
> 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
>
prev parent reply other threads:[~2020-02-07 16:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 15:47 [PATCH 1/2] manpage: Add a description of the 'nconnect' mount option Steve Dickson
2020-01-29 15:47 ` [PATCH 2/2] manpage: Add a description of the 'softreval' / 'nosoftreval' " Steve Dickson
2020-02-07 16:08 ` Steve Dickson
2020-02-03 15:15 ` [PATCH 1/2] manpage: Add a description of the 'nconnect' " Olga Kornievskaia
2020-02-04 16:46 ` Steve Dickson
2020-02-04 17:13 ` Trond Myklebust
2020-02-04 17:22 ` Olga Kornievskaia
2020-02-04 17:36 ` Trond Myklebust
2020-02-07 16:08 ` Steve Dickson [this message]
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=d1a3745e-cda0-d84c-3cff-47d23df105cb@RedHat.com \
--to=steved@redhat.com \
--cc=linux-nfs@vger.kernel.org \
/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