Linux NFS development
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: "Aurélien Couderc" <aurelien.couderc2002@gmail.com>
Cc: NeilBrown <neil@brown.name>, Jeff Layton <jlayton@kernel.org>,
	Olga Kornievskaia <okorniev@redhat.com>,
	Dai Ngo <dai.ngo@oracle.com>, Tom Talpey <tom@talpey.com>,
	linux-nfs@vger.kernel.org, Chuck Lever <chuck.lever@oracle.com>
Subject: Re: [RFC PATCH] Revert "NFSD: Force all NFSv4.2 COPY requests to be synchronous"
Date: Sun, 13 Jul 2025 13:50:09 -0400	[thread overview]
Message-ID: <f6f3c22f-8c49-4f9a-937f-2103cd780f6e@kernel.org> (raw)
In-Reply-To: <CA+1jF5pP3MJQ6L8TBzfuBNRr-YZxefBpBrQSxRR2kJWSqjgYxQ@mail.gmail.com>

On 7/12/25 9:06 AM, Aurélien Couderc wrote:
> ?
> 
> On Wed, Jun 18, 2025 at 9:22 PM Aurélien Couderc
> <aurelien.couderc2002@gmail.com> wrote:
>>
>> On Wed, Jun 18, 2025 at 2:58 PM Chuck Lever <cel@kernel.org> wrote:
>>>
>>> From: Chuck Lever <chuck.lever@oracle.com>
>>>
>>> In the past several kernel releases, we've made NFSv4.2 async copy
>>> reliable:
>>>  - The Linux NFS client and server now both implement and use the
>>>    NFSv4.2 OFFLOAD_STATUS operation
>>>  - The Linux NFS server keeps copy stateids around longer
>>>  - The Linux NFS client and server now both implement referring call
>>>    lists
>>>
>>> And resilient against DoS:
>>>  - The Linux NFS server limits the number of concurrent async copy
>>>    operations
>>
>> And how does an amin change that limit? There is zero documentation
>> for admins, and zero training or reference material for COPY, CLONE,
>> ALLOCATE, ...
>>
>> Aurélien
>> --
>> Aurélien Couderc <aurelien.couderc2002@gmail.com>
>> Big Data/Data mining expert, chess enthusiast
> 
> 
> 

The tone of your original email suggested to me that it was a whine
rather than a genuine request for more information.

Also the request for "training material" for individual NFSv4.2
operations does not make sense. We do not have training material for
the NFSv3 READDIRPLUS procedure, for example.

Therefore I ignored the email.

If you want reference material, the obvious place to look is the
Internet standard that specifies these new operations (RFC 7862). It is
publicly accessible on the web. If you need something more basic, I
highly recommend Callaghan's "NFS Illustrated" (ISBN: 9780321618924).

NFSv4.2 COPY, CLONE, and ALLOCATE are exposed to applications via the
POSIX file system API available in Linux, as documented in man pages.

There is no specific administrative setting that controls the number
of concurrent asynchronous COPY operations. The limit increases with
the number of NFSD threads. If someone demonstrates a specific use
case where manually adjusting that limit is necessary, a setting can
be implemented.

The specific guidance you might be looking for is typically provided
by the documentation staff at Linux distributions. You could file an
issue with your favorite Linux vendor to let them know what you are
looking for.

-- 
Chuck Lever

  reply	other threads:[~2025-07-13 17:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-18 12:58 [RFC PATCH] Revert "NFSD: Force all NFSv4.2 COPY requests to be synchronous" Chuck Lever
2025-06-18 13:02 ` Jeff Layton
2025-06-18 19:22 ` Aurélien Couderc
2025-07-12 13:06   ` Aurélien Couderc
2025-07-13 17:50     ` Chuck Lever [this message]
2025-07-14 10:36       ` Aurélien Couderc
2025-07-14 10:38         ` Aurélien Couderc
2025-07-14 13:59         ` Chuck Lever

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=f6f3c22f-8c49-4f9a-937f-2103cd780f6e@kernel.org \
    --to=cel@kernel.org \
    --cc=aurelien.couderc2002@gmail.com \
    --cc=chuck.lever@oracle.com \
    --cc=dai.ngo@oracle.com \
    --cc=jlayton@kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neil@brown.name \
    --cc=okorniev@redhat.com \
    --cc=tom@talpey.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