NFSv4.1 COMMIT of all changed areas only on flush? Re: [PATCH 06/10] NFSD: Enable return of an updated stable_how to NFS clients

Cedric Blancher <[email protected]> Sat, 30 May 2026 09:58:00 +0200

Newsgroups	gmane.linux.nfs,gmane.ietf.nfsv4,gmane.linux.kernel
Message-ID	<CALXu0Ud9542MSqpbKTWweoCbwJcX7gnzUW8yDT-2=YCoWLt2dQ@mail.gmail.com>

On Fri, 29 May 2026 at 00:03, Jeff Layton <[email protected]> wrote:
>
> From: Chuck Lever <[email protected]>
>
> In a subsequent patch, nfsd_vfs_write() will promote an UNSTABLE
> WRITE to be a FILE_SYNC WRITE. This indicates that the client does
> not need a subsequent COMMIT operation, saving a round trip and
> allowing the client to dispense with cached dirty data as soon as
> it receives the server's WRITE response.
>
> This patch refactors nfsd_vfs_write() to return a possibly modified
> stable_how value to its callers. No behavior change is expected.

Question: Could the NFS client just record the write position and
length, and only ask for a COMMIT when a flush is explicitly issued?

Ced
-- 
Cedric Blancher <[email protected]>
[https://plus.google.com/u/0/+CedricBlancher/]
Institute Pasteur