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 1/5] docs: sysctl: remove references to inode-max
Date: Tue, 12 Jul 2022 19:26:15 +0200 [thread overview]
Message-ID: <20220712172619.359052-1-steve@sk2.org> (raw)
inode-max was removed in 2.3.20pre1, remove references to it in the
sysctl documentation.
Signed-off-by: Stephen Kitt <steve@sk2.org>
---
Documentation/admin-guide/sysctl/fs.rst | 16 ++++------------
1 file changed, 4 insertions(+), 12 deletions(-)
diff --git a/Documentation/admin-guide/sysctl/fs.rst b/Documentation/admin-guide/sysctl/fs.rst
index 2a501c9ddc55..54130ae33df8 100644
--- a/Documentation/admin-guide/sysctl/fs.rst
+++ b/Documentation/admin-guide/sysctl/fs.rst
@@ -33,7 +33,6 @@ Currently, these files are in /proc/sys/fs:
- dquot-nr
- file-max
- file-nr
-- inode-max
- inode-nr
- inode-state
- nr_open
@@ -136,18 +135,12 @@ enough for most machines. Actual limit depends on RLIMIT_NOFILE
resource limit.
-inode-max, inode-nr & inode-state
----------------------------------
+inode-nr & inode-state
+----------------------
As with file handles, the kernel allocates the inode structures
dynamically, but can't free them yet.
-The value in inode-max denotes the maximum number of inode
-handlers. This value should be 3-4 times larger than the value
-in file-max, since stdin, stdout and network sockets also
-need an inode struct to handle them. When you regularly run
-out of inodes, you need to increase this value.
-
The file inode-nr contains the first two items from
inode-state, so we'll skip to that file...
@@ -156,11 +149,10 @@ The actual numbers are, in order of appearance, nr_inodes,
nr_free_inodes and preshrink.
Nr_inodes stands for the number of inodes the system has
-allocated, this can be slightly more than inode-max because
-Linux allocates them one pageful at a time.
+allocated.
Nr_free_inodes represents the number of free inodes (?) and
-preshrink is nonzero when the nr_inodes > inode-max and the
+preshrink is nonzero when the
system needs to prune the inode list instead of allocating
more.
base-commit: 50fd82b3a9a9335df5d50c7ddcb81c81d358c4fc
--
2.31.1
next reply other threads:[~2022-07-12 17:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 17:26 Stephen Kitt [this message]
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 ` [PATCH 4/5] docs: sysctl/fs: remove references to super-max/-nr Stephen Kitt
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-1-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®