From: Jeff Layton <jlayton@kernel.org>
To: Cedric Blancher <cedric.blancher@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: NFSv4.1 --> NFSv4.2 client implementation?
Date: Sat, 18 Nov 2023 07:01:11 -0500 [thread overview]
Message-ID: <d6c218f85f314f28ba94726038782ffada3a2e01.camel@kernel.org> (raw)
In-Reply-To: <CALXu0UcwVRxbG9HD_0U2oK5Le53F3NKQz_H4P4nEesnoWM=BRw@mail.gmail.com>
On Sat, 2023-11-18 at 08:53 +0100, Cedric Blancher wrote:
> Good morning!
>
> What are the differences between NFSv4.1 and NFSv4.2 for a NFSv4
> client, if we ignore server-side copy and READ_PLUS support?
> Can a NFSv4.1 client then identify itself als NFSv4.2 client?
>
Yes. I believe that NFSv4.2 consists entirely of optional features over
NFSv4.1, so it's legitimate for a client or server to advertise itself
as a v4.2 capable, but support none of the features.
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-11-18 12:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-18 7:53 NFSv4.1 --> NFSv4.2 client implementation? Cedric Blancher
2023-11-18 12:01 ` Jeff Layton [this message]
2023-11-19 16:58 ` Cedric Blancher
2023-11-19 17:20 ` Anna Schumaker
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=d6c218f85f314f28ba94726038782ffada3a2e01.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=cedric.blancher@gmail.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