From: Al Viro <viro@zeniv.linux.org.uk>
To: Jinliang Zheng <alexjlzheng@gmail.com>
Cc: brauner@kernel.org, jack@suse.cz, mcgrof@kernel.org,
kees@kernel.org, joel.granados@kernel.org, adobriyan@gmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
flyingpeng@tencent.com, Jinliang Zheng <alexjlzheng@tencent.com>
Subject: Re: [PATCH 0/6] Maintain the relative size of fs.file-max and fs.nr_open
Date: Sat, 23 Nov 2024 18:27:30 +0000 [thread overview]
Message-ID: <20241123182730.GS3387508@ZenIV> (raw)
In-Reply-To: <20241123180901.181825-1-alexjlzheng@tencent.com>
On Sun, Nov 24, 2024 at 02:08:55AM +0800, Jinliang Zheng wrote:
> According to Documentation/admin-guide/sysctl/fs.rst, fs.nr_open and
> fs.file-max represent the number of file-handles that can be opened
> by each process and the entire system, respectively.
>
> Therefore, it's necessary to maintain a relative size between them,
> meaning we should ensure that files_stat.max_files is not less than
> sysctl_nr_open.
NAK.
You are confusing descriptors (nr_open) and open IO channels (max_files).
We very well _CAN_ have more of the former. For further details,
RTFM dup(2) or any introductory Unix textbook.
next prev parent reply other threads:[~2024-11-23 18:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-23 18:08 [PATCH 0/6] Maintain the relative size of fs.file-max and fs.nr_open Jinliang Zheng
2024-11-23 18:11 ` [PATCH 1/6] fs: fix proc_handler for sysctl_nr_open Jinliang Zheng
2024-11-23 18:11 ` [PATCH 2/6] fs: make files_stat globally visible Jinliang Zheng
2024-11-23 18:12 ` [PATCH 3/6] sysctl: refactor __do_proc_doulongvec_minmax() Jinliang Zheng
2024-11-23 18:12 ` [PATCH 4/6] sysctl: ensure files_stat.max_files is not less than sysctl_nr_open Jinliang Zheng
2024-11-23 18:13 ` [PATCH 5/6] sysctl: ensure sysctl_nr_open is not greater than files_stat.max_files Jinliang Zheng
2024-11-23 18:13 ` [PATCH 6/6] fs: synchronize the access of fs.file-max and fs.nr_open Jinliang Zheng
2024-11-23 18:27 ` Al Viro [this message]
2024-11-23 19:32 ` [PATCH 0/6] Maintain the relative size " Al Viro
2024-11-24 2:30 ` Theodore Ts'o
2024-11-24 9:48 ` Jinliang Zheng
2024-11-24 15:59 ` Theodore Ts'o
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=20241123182730.GS3387508@ZenIV \
--to=viro@zeniv.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=alexjlzheng@gmail.com \
--cc=alexjlzheng@tencent.com \
--cc=brauner@kernel.org \
--cc=flyingpeng@tencent.com \
--cc=jack@suse.cz \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.