From: "Li,Rongqing" <lirongqing@baidu.com>
To: Christian Brauner <brauner@kernel.org>
Cc: "viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"jack@suse.cz" <jack@suse.cz>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 答复: [外部邮件] Re: (subset) [PATCH] fs: Make file-nr output the total allocated file handles
Date: Mon, 14 Apr 2025 11:05:48 +0000 [thread overview]
Message-ID: <0c3d84f1b91145ccba7d6d3222962be0@baidu.com> (raw)
In-Reply-To: <20250414-teuflisch-nahezu-396209d549ba@brauner>
> On Thu, 10 Apr 2025 19:21:17 +0800, lirongqing wrote:
> > Make file-nr output the total allocated file handles, not per-cpu
> > cache number, it's more precise, and not in hot path
> >
> >
>
Hi Christian Brauner:
Could we change the changelog as below, it maybe more reasonable
fs: Use percpu_counter_sum_positive in proc_nr_files
The centralized value of percpu counter can be really grossly inaccurate
as CPU count increases. and proc_nr_files is only accessed when reading
proc file, not a hot path, so use percpu_counter_sum_positive in it, to make
/proc/sys/fs/file-nr more accurate
thanks
-Li
> Applied to the vfs-6.16.misc branch of the vfs/vfs.git tree.
> Patches in the vfs-6.16.misc branch should appear in linux-next soon.
>
> Please report any outstanding bugs that were missed during review in a new
> review to the original patch series allowing us to drop it.
>
> It's encouraged to provide Acked-bys and Reviewed-bys even though the patch
> has now been applied. If possible patch trailers will be updated.
>
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
>
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs-6.16.misc
>
> [1/1] fs: Make file-nr output the total allocated file handles
> https://git.kernel.org/vfs/vfs/c/66319519f89d
prev parent reply other threads:[~2025-04-14 11:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 11:21 lirongqing
2025-04-11 14:16 ` Christian Brauner
2025-04-11 21:15 ` Mateusz Guzik
2025-04-12 12:59 ` 答复: [外部邮件] " Li,Rongqing
2025-04-14 10:07 ` (subset) " Christian Brauner
2025-04-14 11:05 ` Li,Rongqing [this message]
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=0c3d84f1b91145ccba7d6d3222962be0@baidu.com \
--to=lirongqing@baidu.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®