From: Stephen Kitt <steve@sk2.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Stephen Kitt <steve@sk2.org>
Subject: [PATCH v2 3/5] docs: sysctl/fs: merge the aio sections
Date: Fri, 30 Sep 2022 12:29:35 +0200 [thread overview]
Message-ID: <20220930102937.135841-4-steve@sk2.org> (raw)
In-Reply-To: <20220930102937.135841-1-steve@sk2.org>
There are two sections documenting aio-nr and aio-max-nr, merge them.
I kept the second explanation of aio-nr, which seems clearer to me,
along with the effects of the values from the first section.
Signed-off-by: Stephen Kitt <steve@sk2.org>
---
Documentation/admin-guide/sysctl/fs.rst | 18 +++++-------------
1 file changed, 5 insertions(+), 13 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/fs.rst b/Documentation/admin-guide/sysctl/fs.rst
index 0935acd220dc..a61c6aec5e5e 100644
--- a/Documentation/admin-guide/sysctl/fs.rst
+++ b/Documentation/admin-guide/sysctl/fs.rst
@@ -50,11 +50,11 @@ Currently, these files are in /proc/sys/fs:
aio-nr & aio-max-nr
-------------------
-aio-nr is the running total of the number of events specified on the
-io_setup system call for all currently active aio contexts. If aio-nr
-reaches aio-max-nr then io_setup will fail with EAGAIN. Note that
-raising aio-max-nr does not result in the pre-allocation or re-sizing
-of any kernel data structures.
+aio-nr shows the current system-wide number of asynchronous io
+requests. aio-max-nr allows you to change the maximum value
+aio-nr can grow to. If aio-nr reaches aio-nr-max then io_setup will
+fail with EAGAIN. Note that raising aio-max-nr does not result in the
+pre-allocation or re-sizing of any kernel data structures.
dentry-state
@@ -287,14 +287,6 @@ mount more filesystems than the current value in super-max
allows you to.
-aio-nr & aio-max-nr
--------------------
-
-aio-nr shows the current system-wide number of asynchronous io
-requests. aio-max-nr allows you to change the maximum value
-aio-nr can grow to.
-
-
mount-max
---------
--
2.31.1
next prev parent reply other threads:[~2022-09-30 14:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 10:29 [PATCH v2 0/5] Update the sysctl/fs documentation Stephen Kitt
2022-09-30 10:29 ` [PATCH v2 1/5] docs: sysctl/fs: remove references to inode-max Stephen Kitt
2022-09-30 10:29 ` [PATCH v2 2/5] docs: sysctl/fs: remove references to dquot-max/-nr Stephen Kitt
2022-09-30 10:29 ` Stephen Kitt [this message]
2022-09-30 10:29 ` [PATCH v2 4/5] docs: sysctl/fs: remove references to super-max/-nr Stephen Kitt
2022-09-30 10:29 ` [PATCH v2 5/5] docs: sysctl/fs: re-order, prettify Stephen Kitt
2022-09-30 10:35 ` [PATCH v2 0/5] Update the sysctl/fs documentation Stephen Kitt
2022-10-19 22:43 ` 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=20220930102937.135841-4-steve@sk2.org \
--to=steve@sk2.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.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).