From: Imran Khan <imran.f.khan@oracle.com>
To: gregkh@linuxfoundation.org, tj@kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [RFC PATCH v2 0/2] kernfs: use kernfs_node specific mutex and spinlock
Date: Mon, 3 Jan 2022 19:45:42 +1100 [thread overview]
Message-ID: <20220103084544.1109829-1-imran.f.khan@oracle.com> (raw)
RFC patchset to reduce usage of global locks in kernfs operations.
PATCH-1: Move kernfs_open_file_mutex and kernfs_open_node_lock within
kernfs_node.
PATCH-2: Use per kernfs_node specific lock to access permissions
------------------------------------------------------------------
Changes since v1:
- Introduce PATCH-2 to reduce contention seen around kernfs_rwsem after
introduction of PATCH-1.
Imran Khan (2):
kernfs: use kernfs_node specific mutex and spinlock.
kernfs: Reduce contention around global per-fs kernfs_rwsem.
fs/kernfs/dir.c | 6 ++++++
fs/kernfs/file.c | 48 +++++++++++++++---------------------------
fs/kernfs/inode.c | 25 +++++++++++++++-------
include/linux/kernfs.h | 3 +++
4 files changed, 43 insertions(+), 39 deletions(-)
base-commit: ea586a076e8aa606c59b66d86660590f18354b11
--
2.30.2
next reply other threads:[~2022-01-03 8:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 8:45 Imran Khan [this message]
2022-01-03 8:45 ` [RFC PATCH v2 1/2] " Imran Khan
2022-01-03 9:54 ` Greg KH
2022-01-03 22:16 ` Imran Khan
2022-01-04 5:48 ` Imran Khan
2022-01-04 7:40 ` Greg KH
2022-01-06 20:30 ` Tejun Heo
2022-01-07 12:01 ` Imran Khan
2022-01-07 13:30 ` Greg KH
2022-01-07 21:25 ` Tejun Heo
2022-01-10 23:42 ` Imran Khan
2022-01-12 20:08 ` Tejun Heo
2022-01-13 8:48 ` Greg KH
2022-01-13 10:51 ` Imran Khan
2022-01-03 8:45 ` [RFC PATCH v2 2/2] kernfs: Reduce contention around global per-fs kernfs_rwsem Imran Khan
2022-01-05 2:17 ` [kernfs] 3dd2a5f81a: INFO:trying_to_register_non-static_key kernel test robot
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=20220103084544.1109829-1-imran.f.khan@oracle.com \
--to=imran.f.khan@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@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 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®