NFSD: nfsd-io-modes: Separate lists

Sphinx reports htmldocs indentation warnings:

Documentation/filesystems/nfs/nfsd-io-modes.rst:58: ERROR: Unexpected indentation. [docutils]
Documentation/filesystems/nfs/nfsd-io-modes.rst:59: WARNING: Block quote ends without a blank line; unexpected unindent. [docutils]

These caused the lists to be shown as long running paragraphs merged
with their previous paragraphs.

Fix these by separating the lists with a blank line.

Fixes: fa8d4e6784 ("NFSD: add Documentation/filesystems/nfs/nfsd-io-modes.rst")
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Closes: https://lore.kernel.org/linux-next/20251202152506.7a2d2d41@canb.auug.org.au/
Signed-off-by: Bagas Sanjaya <bagasdotme@gmail.com>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Tested-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
pull/1354/merge
Bagas Sanjaya 2025-12-03 08:09:11 +07:00 committed by Chuck Lever
parent 4fcf9952fb
commit df8c841dd9
1 changed files with 5 additions and 0 deletions

View File

@ -13,6 +13,7 @@ to override that default to use either DONTCACHE or DIRECT IO modes.
Experimental NFSD debugfs interfaces are available to allow the NFSD IO Experimental NFSD debugfs interfaces are available to allow the NFSD IO
mode used for READ and WRITE to be configured independently. See both: mode used for READ and WRITE to be configured independently. See both:
- /sys/kernel/debug/nfsd/io_cache_read - /sys/kernel/debug/nfsd/io_cache_read
- /sys/kernel/debug/nfsd/io_cache_write - /sys/kernel/debug/nfsd/io_cache_write
@ -20,6 +21,7 @@ The default value for both io_cache_read and io_cache_write reflects
NFSD's default IO mode (which is NFSD_IO_BUFFERED=0). NFSD's default IO mode (which is NFSD_IO_BUFFERED=0).
Based on the configured settings, NFSD's IO will either be: Based on the configured settings, NFSD's IO will either be:
- cached using page cache (NFSD_IO_BUFFERED=0) - cached using page cache (NFSD_IO_BUFFERED=0)
- cached but removed from page cache on completion (NFSD_IO_DONTCACHE=1) - cached but removed from page cache on completion (NFSD_IO_DONTCACHE=1)
- not cached stable_how=NFS_UNSTABLE (NFSD_IO_DIRECT=2) - not cached stable_how=NFS_UNSTABLE (NFSD_IO_DIRECT=2)
@ -56,6 +58,7 @@ because the page cache will eventually become a bottleneck to servicing
new IO requests. new IO requests.
For more context on DONTCACHE, please see these Linux commit headers: For more context on DONTCACHE, please see these Linux commit headers:
- Overview: 9ad6344568cc3 ("mm/filemap: change filemap_create_folio() - Overview: 9ad6344568cc3 ("mm/filemap: change filemap_create_folio()
to take a struct kiocb") to take a struct kiocb")
- for READ: 8026e49bff9b1 ("mm/filemap: add read support for - for READ: 8026e49bff9b1 ("mm/filemap: add read support for
@ -87,7 +90,9 @@ be made.
The performance win associated with using NFSD DIRECT was previously The performance win associated with using NFSD DIRECT was previously
discussed on linux-nfs, see: discussed on linux-nfs, see:
https://lore.kernel.org/linux-nfs/aEslwqa9iMeZjjlV@kernel.org/ https://lore.kernel.org/linux-nfs/aEslwqa9iMeZjjlV@kernel.org/
But in summary: But in summary:
- NFSD DIRECT can significantly reduce memory requirements - NFSD DIRECT can significantly reduce memory requirements
- NFSD DIRECT can reduce CPU load by avoiding costly page reclaim work - NFSD DIRECT can reduce CPU load by avoiding costly page reclaim work
- NFSD DIRECT can offer more deterministic IO performance - NFSD DIRECT can offer more deterministic IO performance