Received-SPF: pass (google.com: domain of linux-nfs-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Scott Mayhew <smayhew@redhat.com>
To:     steved@redhat.com
Cc:     linux-nfs@vger.kernel.org
Subject: [nfs-utils PATCH 2/3] nfs(5): Document the write=lazy|eager|wait mount option.
Date:   Thu,  1 Jun 2023 15:46:16 -0400
Message-Id: <20230601194617.2174639-3-smayhew@redhat.com>
In-Reply-To: <20230601194617.2174639-1-smayhew@redhat.com>
References: <20230601194617.2174639-1-smayhew@redhat.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk

Signed-off-by: Scott Mayhew <smayhew@redhat.com>
---
 utils/mount/nfs.man | 22 ++++++++++++++++++++++
 1 file changed, 22 insertions(+)

diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index 3cef2e23..2ed898f8 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -614,6 +614,28 @@ option is not specified,
 the default behavior depends on the kernel,
 but is usually equivalent to
 .BR "xprtsec=none" .
+.TP 1.5i
+.BI write= behavior
+Controls how the NFS client handles the
+.BR write (2)
+system call.
+.I behavior
+can be one of
+.BR lazy ,
+.BR eager ,
+or
+.BR wait .
+If
+.B lazy
+(the default) is specified, then the NFS client delays sending application
+writes to the NFS server as described in the DATA AND METADATA COHERENCE
+section.  If
+.B eager
+is specified, then the NFS client sends off the write immediately as an
+unstable WRITE to the NFS server.  If
+.B wait
+is specified, then the NFS client sends off the write immediately as an
+unstable WRITE to the NFS server and then waits for the reply.
 .SS "Options for NFS versions 2 and 3 only"
 Use these options, along with the options in the above subsection,
 for NFS versions 2 and 3 only.
-- 
2.39.2