From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
To: mchehab+samsung@kernel.org, corbet@lwn.net
Cc: linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org,
"Daniel W. S. Almeida" <dwlsalmeida@gmail.com>,
linux-doc@vger.kernel.org
Subject: [Linux-kernel-mentees] [PATCH v4 5/9] Documentation: convert nfsd-admin-interfaces to ReST
Date: Fri, 10 Jan 2020 20:24:27 -0300 [thread overview]
Message-ID: <d471305e9c96dec38f18d2ff816fca2269a88e29.1578697871.git.dwlsalmeida@gmail.com> (raw)
In-Reply-To: <cover.1578697871.git.dwlsalmeida@gmail.com>
From: "Daniel W. S. Almeida" <dwlsalmeida@gmail.com>
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>
---
Documentation/admin-guide/nfs/index.rst | 1 +
.../nfs/nfsd-admin-interfaces.rst} | 19 +++++++++----------
2 files changed, 10 insertions(+), 10 deletions(-)
rename Documentation/{filesystems/nfs/nfsd-admin-interfaces.txt => admin-guide/nfs/nfsd-admin-interfaces.rst} (70%)
diff --git a/Documentation/admin-guide/nfs/index.rst b/Documentation/admin-guide/nfs/index.rst
index 875a96fe9d04..e0b2f4260ad7 100644
--- a/Documentation/admin-guide/nfs/index.rst
+++ b/Documentation/admin-guide/nfs/index.rst
@@ -8,3 +8,4 @@ NFS
nfs-client
nfsroot
nfs-rdma
+ nfsd-admin-interfaces
diff --git a/Documentation/filesystems/nfs/nfsd-admin-interfaces.txt b/Documentation/admin-guide/nfs/nfsd-admin-interfaces.rst
similarity index 70%
rename from Documentation/filesystems/nfs/nfsd-admin-interfaces.txt
rename to Documentation/admin-guide/nfs/nfsd-admin-interfaces.rst
index 56a96fb08a73..c05926f79054 100644
--- a/Documentation/filesystems/nfs/nfsd-admin-interfaces.txt
+++ b/Documentation/admin-guide/nfs/nfsd-admin-interfaces.rst
@@ -1,5 +1,6 @@
+==================================
Administrative interfaces for nfsd
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+==================================
Note that normally these interfaces are used only by the utilities in
nfs-utils.
@@ -13,18 +14,16 @@ nfsd/threads.
Before doing that, NFSD can be told which sockets to listen on by
writing to nfsd/portlist; that write may be:
- - an ascii-encoded file descriptor, which should refer to a
- bound (and listening, for tcp) socket, or
- - "transportname port", where transportname is currently either
- "udp", "tcp", or "rdma".
+ - an ascii-encoded file descriptor, which should refer to a
+ bound (and listening, for tcp) socket, or
+ - "transportname port", where transportname is currently either
+ "udp", "tcp", or "rdma".
If nfsd is started without doing any of these, then it will create one
udp and one tcp listener at port 2049 (see nfsd_init_socks).
-On startup, nfsd and lockd grace periods start.
-
-nfsd is shut down by a write of 0 to nfsd/threads. All locks and state
-are thrown away at that point.
+On startup, nfsd and lockd grace periods start. nfsd is shut down by a write of
+0 to nfsd/threads. All locks and state are thrown away at that point.
Between startup and shutdown, the number of threads may be adjusted up
or down by additional writes to nfsd/threads or by writes to
@@ -34,7 +33,7 @@ For more detail about files under nfsd/ and what they control, see
fs/nfsd/nfsctl.c; most of them have detailed comments.
Implementation notes
-^^^^^^^^^^^^^^^^^^^^
+====================
Note that the rpc server requires the caller to serialize addition and
removal of listening sockets, and startup and shutdown of the server.
--
2.24.1
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-01-10 23:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 23:24 [Linux-kernel-mentees] [PATCH v4 0/9] Documentation: nfs: Convert a few documents to RST and move them to admin-guide Daniel W. S. Almeida
2020-01-10 23:24 ` [Linux-kernel-mentees] [PATCH v4 1/9] Documentation: convert nfs.txt to ReST Daniel W. S. Almeida
2020-01-10 23:24 ` [Linux-kernel-mentees] [PATCH v4 2/9] Documentation: nfsroot.txt: convert " Daniel W. S. Almeida
2020-01-10 23:24 ` [Linux-kernel-mentees] [PATCH v4 3/9] Documentation: nfsroot.rst: COSMETIC: refill a paragraph Daniel W. S. Almeida
2020-01-10 23:24 ` [Linux-kernel-mentees] [PATCH v4 4/9] Documentation: nfs-rdma: convert to ReST Daniel W. S. Almeida
2020-01-10 23:24 ` Daniel W. S. Almeida [this message]
2020-01-10 23:24 ` [Linux-kernel-mentees] [PATCH v4 6/9] Documentation: nfs: idmapper: " Daniel W. S. Almeida
2020-01-10 23:24 ` [Linux-kernel-mentees] [PATCH v4 7/9] Documentation: nfs: convert pnfs-block-server " Daniel W. S. Almeida
2020-01-10 23:24 ` [Linux-kernel-mentees] [PATCH v4 8/9] Documentation: nfs: pnfs-scsi-server: convert " Daniel W. S. Almeida
2020-01-10 23:24 ` [Linux-kernel-mentees] [PATCH v4 9/9] Documentation: nfs: fault_injection: " Daniel W. S. Almeida
2020-01-16 19:51 ` [Linux-kernel-mentees] [PATCH v4 0/9] Documentation: nfs: Convert a few documents to RST and move them to admin-guide Jonathan Corbet
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d471305e9c96dec38f18d2ff816fca2269a88e29.1578697871.git.dwlsalmeida@gmail.com \
--to=dwlsalmeida@gmail.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).