From: Huang Shijie <huangsj@hygon.cn>
To: <viro@zeniv.linux.org.uk>, <brauner@kernel.org>
Cc: <zhongyuan@hygon.cn>, <fangbaoshun@hygon.cn>,
<yingzhiwei@hygon.cn>, <jack@suse.cz>, <dev.jain@arm.com>,
<ljs@kernel.org>, <adobriyan@gmail.com>,
<akpm@linux-foundation.org>, <hpa@zytor.com>,
<ryan.roberts@arm.com>, <mjguzik@gmail.com>,
<joel.granados@kernel.org>, <jannh@google.com>, <oleg@redhat.com>,
<aleksa@amutable.com>, <legion@kernel.org>, <kees@kernel.org>,
<joannelkoong@gmail.com>, <tj@kernel.org>,
<libaokun@linux.alibaba.com>, <ebiggers@kernel.org>,
<sandeen@redhat.com>, <linux-fsdevel@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Huang Shijie <huangsj@hygon.cn>
Subject: [RFC PATCH v2 0/3] fs/proc: split the inode list for procfs
Date: Sun, 20 Sep 2026 15:28:08 +0800 [thread overview]
Message-ID: <20260920072811.2064247-1-huangsj@hygon.cn> (raw)
The global s_inode_list_lock is heavily contended in procfs
on a 384-CPU, 12-NUMA-node Hygon machine running Hadoop TestDFSIO:
#hadoop jar xxxx.jar TestDFSIO -read -nrFiles 1000 -size 100MB
The hadoop will create lot of threads during the test.
The perf shows it consuming ~90% of the lock hotspot in procfs.
The lock is hit from both directions:
-- inode creation (~49%) :
getdents64 ->
proc_readfd_common ->
new_inode ->
inode_sb_list_add()
-- inode eviction (~41%):
process exit ->
release_task ->
proc_invalidate_siblings_dcache ->
evict ->
inode_sb_list_del()
This patch set tries to resolve this issue by:
patch 1: "fs/drop_caches: skip filesystems without page cache"
add a new flag for filesystems without page cache.
patch 2: Add a new helper to detect the empty inode list
patch 3: split the inode list.
After this patch set, the above TestDFSIO can get over 50% better performance
in exec time. And the procfs lock hotspot becomes nearly 1%.
Huang Shijie (3):
fs/drop_caches: skip filesystems without page cache
fs/super: introduce a helper sb_inodes_empty()
fs/proc: split the inode list
fs/drop_caches.c | 3 +
fs/inode.c | 79 ++++++++++------
fs/proc/inode.c | 53 +++++++++++
fs/proc/internal.h | 2 +
fs/proc/root.c | 8 +-
fs/super.c | 45 +++++++--
include/linux/fs/super_types.h | 17 ++++
include/linux/proc_fs.h | 1 +
security/landlock/fs.c | 162 ++++++++++++++++++---------------
9 files changed, 260 insertions(+), 110 deletions(-)
--
2.53.0
next reply other threads:[~2026-09-20 7:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 7:28 Huang Shijie [this message]
2026-09-20 7:28 ` [RFC PATCH v2 1/3] fs/drop_caches: skip filesystems without page cache Huang Shijie
2026-09-20 7:28 ` [RFC PATCH v2 2/3] fs/super: introduce a helper sb_inodes_empty() Huang Shijie
2026-09-20 7:28 ` [RFC PATCH v2 3/3] fs/proc: split the inode list Huang Shijie
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=20260920072811.2064247-1-huangsj@hygon.cn \
--to=huangsj@hygon.cn \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=aleksa@amutable.com \
--cc=brauner@kernel.org \
--cc=dev.jain@arm.com \
--cc=ebiggers@kernel.org \
--cc=fangbaoshun@hygon.cn \
--cc=hpa@zytor.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=joannelkoong@gmail.com \
--cc=joel.granados@kernel.org \
--cc=kees@kernel.org \
--cc=legion@kernel.org \
--cc=libaokun@linux.alibaba.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=mjguzik@gmail.com \
--cc=oleg@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=sandeen@redhat.com \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=yingzhiwei@hygon.cn \
--cc=zhongyuan@hygon.cn \
/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®