From: Stephen Kitt <steve@sk2.org>
To: Jonathan Corbet <corbet@lwn.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
Stephen Kitt <steve@sk2.org>
Subject: [PATCH 4/5] docs: sysctl/fs: remove references to super-max/-nr
Date: Tue, 12 Jul 2022 19:26:18 +0200 [thread overview]
Message-ID: <20220712172619.359052-4-steve@sk2.org> (raw)
In-Reply-To: <20220712172619.359052-1-steve@sk2.org>
These were removed in 2.4.7.8. Remove references to super-max and
super-nr in the sysctl documentation.
Signed-off-by: Stephen Kitt <steve@sk2.org>
---
Documentation/admin-guide/sysctl/fs.rst | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/fs.rst b/Documentation/admin-guide/sysctl/fs.rst
index a61c6aec5e5e..df683c15b098 100644
--- a/Documentation/admin-guide/sysctl/fs.rst
+++ b/Documentation/admin-guide/sysctl/fs.rst
@@ -277,16 +277,6 @@ or otherwise protected/tainted binaries. The modes are
= ========== ===============================================================
-super-max & super-nr
---------------------
-
-These numbers control the maximum number of superblocks, and
-thus the maximum number of mounted filesystems the kernel
-can have. You only need to increase super-max if you need to
-mount more filesystems than the current value in super-max
-allows you to.
-
-
mount-max
---------
--
2.31.1
next prev parent reply other threads:[~2022-07-12 17:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:26 [PATCH 1/5] docs: sysctl: remove references to inode-max Stephen Kitt
2022-07-12 17:26 ` [PATCH 2/5] docs: sysctl: remove references to dquot-max/-nr Stephen Kitt
2022-07-12 17:26 ` [PATCH 3/5] docs: sysctl/fs: merge the aio sections Stephen Kitt
2022-07-12 17:26 ` Stephen Kitt [this message]
2022-07-12 17:26 ` [PATCH 5/5] docs: sysctl/fs: re-order, prettify Stephen Kitt
2022-07-16 19:44 ` kernel test robot
2022-07-13 20:07 ` [PATCH 1/5] docs: sysctl: remove references to inode-max 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=20220712172619.359052-4-steve@sk2.org \
--to=steve@sk2.org \
--cc=corbet@lwn.net \
--cc=linux-doc@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
all inboxes | Powered by JetHome®