From: Imran Khan <imran.f.khan@oracle.com>
To: tj@kernel.org, viro@zeniv.linux.org.uk, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 0/5] kernfs: Remove reference counting for kernfs_open_node.
Date: Thu, 28 Apr 2022 15:54:26 +1000 [thread overview]
Message-ID: <20220428055431.3826852-1-imran.f.khan@oracle.com> (raw)
This patchset contains subset of patches (after addressing review comments)
discussed at [1]. Since [1] is replacing multiple global locks and since
each of these locks can be removed independently, it was decided that we
should make these changes in parts i.e first get one set of optimizations
integrated and then work on top of those further.
The patches in this change set introduce following changes:
PATCH-1: Remove reference counting for kernfs_open_node.
PATCH-2: Make kernfs_open_node->attr.open RCU protected.
PATCH-3: Change kernfs_notify_list to llist.
PATCH-4: Introduce interface to access kernfs_open_file_mutex.
PATCH-5: Replace global kernfs_open_file_mutex with hashed mutexes.
-------------------------------------------------------------------------
Imran Khan (5):
kernfs: Remove reference counting for kernfs_open_node.
kernfs: make ->attr.open RCU protected.
kernfs: Change kernfs_notify_list to llist.
kernfs: Introduce interface to access global kernfs_open_file_mutex.
kernfs: Replace global kernfs_open_file_mutex with hashed mutexes.
fs/kernfs/file.c | 247 ++++++++++++++++++++----------------
fs/kernfs/kernfs-internal.h | 4 +
fs/kernfs/mount.c | 19 +++
include/linux/kernfs.h | 61 ++++++++-
4 files changed, 223 insertions(+), 108 deletions(-)
base-commit: 088fb7eff3496e0f61fdf68bda89b81a4d0a4434
[1] https://lore.kernel.org/lkml/YmLfxHcekrr89IFl@slm.duckdns.org/
--
2.30.2
next reply other threads:[~2022-04-28 5:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 5:54 Imran Khan [this message]
2022-04-28 5:54 ` [PATCH 1/5] kernfs: Remove reference counting for kernfs_open_node Imran Khan
2022-05-05 19:46 ` Tejun Heo
2022-04-28 5:54 ` [PATCH 2/5] kernfs: make ->attr.open RCU protected Imran Khan
2022-05-05 20:01 ` Tejun Heo
2022-05-05 23:12 ` Imran Khan
2022-05-12 17:09 ` Tejun Heo
2022-05-15 16:00 ` Imran Khan
2022-05-16 19:35 ` Tejun Heo
2022-05-17 2:30 ` Imran Khan
2022-05-17 4:21 ` Tejun Heo
2022-04-28 5:54 ` [PATCH 3/5] kernfs: Change kernfs_notify_list to llist Imran Khan
2022-05-05 20:03 ` Tejun Heo
2022-04-28 5:54 ` [PATCH 4/5] kernfs: Introduce interface to access global kernfs_open_file_mutex Imran Khan
2022-05-05 20:04 ` Tejun Heo
2022-04-28 5:54 ` [PATCH 5/5] kernfs: Replace global kernfs_open_file_mutex with hashed mutexes Imran Khan
2022-05-05 20:05 ` Tejun Heo
2022-05-11 9:58 ` Imran Khan
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=20220428055431.3826852-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 \
--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).