From: chenzhiyin <zhiyin.chen@intel.com>
To: viro@zeniv.linux.org.uk, brauner@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
nanhai.zou@intel.com, zhiyin.chen@intel.com
Subject: [PATCH] fs.h: Optimize file struct to prevent false sharing
Date: Mon, 29 May 2023 22:06:26 -0400 [thread overview]
Message-ID: <20230530020626.186192-1-zhiyin.chen@intel.com> (raw)
In the syscall test of UnixBench, performance regression occurred
due to false sharing.
The lock and atomic members, including file::f_lock, file::f_count
and file::f_pos_lock are highly contended and frequently updated
in the high-concurrency test scenarios. perf c2c indentified one
affected read access, file::f_op.
To prevent false sharing, the layout of file struct is changed as
following
(A) f_lock, f_count and f_pos_lock are put together to share the
same cache line.
(B) The read mostly members, including f_path, f_inode, f_op are
put into a separate cache line.
(C) f_mode is put together with f_count, since they are used
frequently at the same time.
The optimization has been validated in the syscall test of
UnixBench. performance gain is 30~50%, when the number of parallel
jobs is 16.
Signed-off-by: chenzhiyin <zhiyin.chen@intel.com>
---
include/linux/fs.h | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 21a981680856..01c55e3a1b96 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -962,23 +962,23 @@ struct file {
struct rcu_head f_rcuhead;
unsigned int f_iocb_flags;
};
- struct path f_path;
- struct inode *f_inode; /* cached value */
- const struct file_operations *f_op;
/*
* Protects f_ep, f_flags.
* Must not be taken from IRQ context.
*/
spinlock_t f_lock;
- atomic_long_t f_count;
- unsigned int f_flags;
fmode_t f_mode;
+ atomic_long_t f_count;
struct mutex f_pos_lock;
+ unsigned int f_flags;
loff_t f_pos;
struct fown_struct f_owner;
const struct cred *f_cred;
struct file_ra_state f_ra;
+ struct path f_path;
+ struct inode *f_inode; /* cached value */
+ const struct file_operations *f_op;
u64 f_version;
#ifdef CONFIG_SECURITY
--
2.39.1
next reply other threads:[~2023-05-30 2:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 2:06 chenzhiyin [this message]
2023-05-30 8:50 ` [PATCH] fs.h: Optimize file struct to prevent false sharing Christian Brauner
2023-05-30 10:02 ` Amir Goldstein
2023-05-31 11:15 ` Christian Brauner
2023-05-31 1:55 ` Eric Biggers
2023-05-31 7:54 ` Christian Brauner
2023-06-01 9:24 ` chenzhiyin
2023-06-01 9:49 ` Christian Brauner
2023-06-01 10:06 ` Bernd Schubert
2023-06-05 12:58 ` Christian Brauner
2023-05-31 10:31 ` Chen, Zhiyin
2023-05-31 22:30 ` Dave Chinner
2023-06-01 10:47 ` Chen, Zhiyin
2023-06-02 0:47 ` Dave Chinner
2023-06-02 11:01 ` Chen, Zhiyin
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=20230530020626.186192-1-zhiyin.chen@intel.com \
--to=zhiyin.chen@intel.com \
--cc=brauner@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nanhai.zou@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).