Skip to content

Commit b38a602

Browse files
committed
Documentation: Add missing documentation for EXPORT_OP flags
The commits that introduced these flags neglected to update the Documentation/filesystems/nfs/exporting.rst file. Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
1 parent 899525e commit b38a602

File tree

1 file changed

+26
-0
lines changed

1 file changed

+26
-0
lines changed

Documentation/filesystems/nfs/exporting.rst

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -215,3 +215,29 @@ following flags are defined:
215215
This flag causes nfsd to close any open files for this inode _before_
216216
calling into the vfs to do an unlink or a rename that would replace
217217
an existing file.
218+
219+
EXPORT_OP_REMOTE_FS - Backing storage for this filesystem is remote
220+
PF_LOCAL_THROTTLE exists for loopback NFSD, where a thread needs to
221+
write to one bdi (the final bdi) in order to free up writes queued
222+
to another bdi (the client bdi). Such threads get a private balance
223+
of dirty pages so that dirty pages for the client bdi do not imact
224+
the daemon writing to the final bdi. For filesystems whose durable
225+
storage is not local (such as exported NFS filesystems), this
226+
constraint has negative consequences. EXPORT_OP_REMOTE_FS enables
227+
an export to disable writeback throttling.
228+
229+
EXPORT_OP_NOATOMIC_ATTR - Filesystem does not update attributes atomically
230+
EXPORT_OP_NOATOMIC_ATTR indicates that the exported filesystem
231+
cannot provide the semantics required by the "atomic" boolean in
232+
NFSv4's change_info4. This boolean indicates to a client whether the
233+
returned before and after change attributes were obtained atomically
234+
with the respect to the requested metadata operation (UNLINK,
235+
OPEN/CREATE, MKDIR, etc).
236+
237+
EXPORT_OP_FLUSH_ON_CLOSE - Filesystem flushes file data on close(2)
238+
On most filesystems, inodes can remain under writeback after the
239+
file is closed. NFSD relies on client activity or local flusher
240+
threads to handle writeback. Certain filesystems, such as NFS, flush
241+
all of an inode's dirty data on last close. Exports that behave this
242+
way should set EXPORT_OP_FLUSH_ON_CLOSE so that NFSD knows to skip
243+
waiting for writeback when closing such files.

0 commit comments

Comments
 (0)