From: Greg KH <gregkh@linuxfoundation.org>
To: Jinliang Zheng <alexjlzheng@gmail.com>
Cc: alexjlzheng@tencent.com, linux-kernel@vger.kernel.org, tj@kernel.org
Subject: Re: [PATCH kernfs 1/3] kernfs: switch global kernfs_idr_lock to per-fs lock
Date: Tue, 15 Apr 2025 17:16:46 +0200 [thread overview]
Message-ID: <2025041506-punk-conflict-ffa3@gregkh> (raw)
In-Reply-To: <20250414032054.72526-1-alexjlzheng@tencent.com>
On Mon, Apr 14, 2025 at 11:20:54AM +0800, Jinliang Zheng wrote:
> > On Sat, Apr 12, 2025 at 07:50:54PM +0800, alexjlzheng@gmail.com wrote:
> > > On Sat, 12 Apr 2025 08:12:22 +0200, gregkh@linuxfoundation.org wrote:
> > > > On Sat, Apr 13, 2025 at 02:31:07AM +0800, alexjlzheng@gmail.com wrote:
> > > > > From: Jinliang Zheng <alexjlzheng@tencent.com>
> > > > >
> > > > > The kernfs implementation has big lock granularity(kernfs_idr_lock) so
> > > > > every kernfs-based(e.g., sysfs, cgroup) fs are able to compete the lock.
> > > > >
> > > > > This patch switches the global kernfs_idr_lock to per-fs lock, which
> > > > > put the spinlock into kernfs_root.
> > > > >
> > > > > Signed-off-by: Jinliang Zheng <alexjlzheng@tencent.com>
> > > > > ---
> > > > > fs/kernfs/dir.c | 14 +++++++-------
> > > > > fs/kernfs/kernfs-internal.h | 1 +
> > > > > 2 files changed, 8 insertions(+), 7 deletions(-)
> > > >
> > > > What kind of testing / benchmark did you do for this series that shows
> > > > that this works, AND that this actually is measureable? What workload
> > > > are you doing that causes these changes to be needed?
> > >
> > > Thank you for your reply. :)
> > >
> > > We are trying to implement a kernfs-based filesystem that will have
> > > multiple instances running at the same time, i.e., multiple kernfs_roots.
> >
> > I don't think that kernfs is meant for that very well, what is that
> > filesystem going to be for?
>
> Thank you for your reply. :)
>
> Similar to cgroupfs and sysfs, it is used to export the status and configurations
> of some kernel variables in hierarchical modes of the kernel. The only difference
> is that it may have many instances, that is, many kernfs_roots.
Let's see that filesystem first please before determining more, as you
would be adding a new user/kernel api that we all need to argue about :)
Anyway, for the 2 patches that Tejun agrees with here, can you resend
just them?
thanks,
greg k-h
next prev parent reply other threads:[~2025-04-15 15:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-11 18:31 [PATCH kernfs 0/3] kernfs: switch global locks to per-fs lock alexjlzheng
2025-04-11 18:31 ` [PATCH kernfs 1/3] kernfs: switch global kernfs_idr_lock " alexjlzheng
2025-04-12 6:12 ` Greg KH
2025-04-12 11:50 ` alexjlzheng
2025-04-13 7:51 ` Greg KH
2025-04-14 3:20 ` Jinliang Zheng
2025-04-15 15:16 ` Greg KH [this message]
2025-04-15 15:44 ` Jinliang Zheng
2025-04-14 17:09 ` Tejun Heo
2025-04-15 6:28 ` Jinliang Zheng
2025-04-11 18:31 ` [PATCH kernfs 2/3] kernfs: switch global kernfs_rename_lock " alexjlzheng
2025-04-14 17:26 ` Tejun Heo
2025-04-11 18:31 ` [PATCH kernfs 3/3] kernfs: switch global kernfs_pr_cont_lock " alexjlzheng
2025-04-14 17:27 ` Tejun Heo
2025-04-15 6:37 ` Jinliang Zheng
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=2025041506-punk-conflict-ffa3@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alexjlzheng@gmail.com \
--cc=alexjlzheng@tencent.com \
--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