inode-max was removed in 2.3.20pre1, remove references to it in the sysctl documentation. Signed-off-by: Stephen Kitt <steve@xxxxxxx> --- 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
