linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@RedHat.com>
To: "Jianhong.Yin" <yin-jianhong@163.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsman: document minorversion
Date: Thu, 14 Sep 2017 13:12:05 -0400	[thread overview]
Message-ID: <558c70e5-c278-0a8c-5ed0-af7637dccd23@RedHat.com> (raw)
In-Reply-To: <20170907065729.4636-1-yin-jianhong@163.com>



On 09/07/2017 02:57 AM, Jianhong.Yin wrote:
> Signed-off-by: Jianhong Yin <yin-jianhong@163.com>
> ---
>  utils/mount/nfs.man | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
Committed....

steved.
> 
> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
> index cc6e992..7d42f19 100644
> --- a/utils/mount/nfs.man
> +++ b/utils/mount/nfs.man
> @@ -779,6 +779,23 @@ so if this mount option is not specified, the NFS version 4 client
>  uses the TCP protocol.
>  Refer to the TRANSPORT METHODS section for more details.
>  .TP 1.5i
> +.BI minorversion= n
> +Specifies the protocol minor version number.
> +NFSv4 introduces "minor versioning," where NFS protocol enhancements can
> +be introduced without bumping the NFS protocol version number.
> +Before kernel 2.6.38, the minor version is always zero, and this
> +option is not recognized.
> +After this kernel, specifying "minorversion=1" enables a number of
> +advanced features, such as NFSv4 sessions.
> +.IP
> +Recent kernels allow the minor version to be specified using the
> +.B vers=
> +option.
> +For example, specifying
> +.B vers=4.1
> +is the same as specifying
> +.BR vers=4,minorversion=1 .
> +.TP 1.5i
>  .BI port= n
>  The numeric value of the server's NFS service port.
>  If the server's NFS service is not available on the specified port,
> 

  reply	other threads:[~2017-09-14 17:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07  6:57 [PATCH] nfsman: document minorversion Jianhong.Yin
2017-09-14 17:12 ` Steve Dickson [this message]
2017-09-15  3:05 ` NeilBrown

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=558c70e5-c278-0a8c-5ed0-af7637dccd23@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=yin-jianhong@163.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).