Received-SPF: pass (google.com: best guess record for domain of linux-nfs-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH 1/2] manpage: Add a description of the 'nconnect' mount
 option
To:     Olga Kornievskaia <aglo@umich.edu>,
        Trond Myklebust <trondmy@hammerspace.com>
Cc:     Linux NFS Mailing list <linux-nfs@vger.kernel.org>
References: <20200129154703.6204-1-steved@redhat.com>
 <CAN-5tyF1NUt2emuPGYF+-3s9cJPwox1uoh0uVzxArRJtzPXMTA@mail.gmail.com>
From:   Steve Dickson <SteveD@RedHat.com>
Message-ID: <4c48901d-3e37-31fc-a032-0326bda51b25@RedHat.com>
Date:   Tue, 4 Feb 2020 11:46:32 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101
 Thunderbird/68.4.1
MIME-Version: 1.0
In-Reply-To: <CAN-5tyF1NUt2emuPGYF+-3s9cJPwox1uoh0uVzxArRJtzPXMTA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-nfs-owner@vger.kernel.org
Precedence: bulk

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@redhat.com> 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>
>> ---
>>  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
>>
>