tjh.dev / kernel
Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux
fork atom

Documentation: convert nfsd-admin-interfaces to ReST

Convert nfsd-admin-interfaces to ReST and move it into admin-guide.
Content remains mostly untouched.

Signed-off-by: Daniel W. S. Almeida <dwlsalmeida@gmail.com>
Link: https://lore.kernel.org/r/d471305e9c96dec38f18d2ff816fca2269a88e29.1578697871.git.dwlsalmeida@gmail.com
Signed-off-by: Jonathan Corbet <corbet@lwn.net>

authored by

Daniel W. S. Almeida and committed by
Jonathan Corbet 0f3456ba f8b8d030

+10 -10
+1
Documentation/admin-guide/nfs/index.rst
··· 8 8 nfs-client 9 9 nfsroot 10 10 nfs-rdma 11 + nfsd-admin-interfaces
+9 -10
Documentation/filesystems/nfs/nfsd-admin-interfaces.txt Documentation/admin-guide/nfs/nfsd-admin-interfaces.rst
··· 1 + ================================== 1 2 Administrative interfaces for nfsd 2 - ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 3 + ================================== 3 4 4 5 Note that normally these interfaces are used only by the utilities in 5 6 nfs-utils. ··· 14 13 Before doing that, NFSD can be told which sockets to listen on by 15 14 writing to nfsd/portlist; that write may be: 16 15 17 - - an ascii-encoded file descriptor, which should refer to a 18 - bound (and listening, for tcp) socket, or 19 - - "transportname port", where transportname is currently either 20 - "udp", "tcp", or "rdma". 16 + - an ascii-encoded file descriptor, which should refer to a 17 + bound (and listening, for tcp) socket, or 18 + - "transportname port", where transportname is currently either 19 + "udp", "tcp", or "rdma". 21 20 22 21 If nfsd is started without doing any of these, then it will create one 23 22 udp and one tcp listener at port 2049 (see nfsd_init_socks). 24 23 25 - On startup, nfsd and lockd grace periods start. 26 - 27 - nfsd is shut down by a write of 0 to nfsd/threads. All locks and state 28 - are thrown away at that point. 24 + On startup, nfsd and lockd grace periods start. nfsd is shut down by a write of 25 + 0 to nfsd/threads. All locks and state are thrown away at that point. 29 26 30 27 Between startup and shutdown, the number of threads may be adjusted up 31 28 or down by additional writes to nfsd/threads or by writes to ··· 33 34 fs/nfsd/nfsctl.c; most of them have detailed comments. 34 35 35 36 Implementation notes 36 - ^^^^^^^^^^^^^^^^^^^^ 37 + ==================== 37 38 38 39 Note that the rpc server requires the caller to serialize addition and 39 40 removal of listening sockets, and startup and shutdown of the server.