From: Greg KH <gregkh@linuxfoundation.org>
To: Imran Khan <imran.f.khan@oracle.com>
Cc: tj@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/2] kernfs: use kernfs_node specific mutex and spinlock.
Date: Tue, 4 Jan 2022 08:40:30 +0100 [thread overview]
Message-ID: <YdP57ij4JxahpdnC@kroah.com> (raw)
In-Reply-To: <719eb5d2-680c-e596-1446-3ca8f47c3aea@oracle.com>
On Tue, Jan 04, 2022 at 09:16:03AM +1100, Imran Khan wrote:
> > There is a tradeoff of memory usage and runtime contention that has to
> > be made here, and this might be pushing it in the wrong direction for
> > a lot of systems.
> >
> Agree. Could you please suggest if this should be made configurable via
> kconfig ? I understand that this would result in 2 versions of some
> functions but it will allow systems with large memories to avoid kernfs
> contention.
No, that way lies madness and horrible bugs and a codebase no one will
be able to maintain.
> We are seeing the launch time of some DB workloads adversely getting
> affected with this contention.
What workloads? sysfs should NEVER be in the fast-path of any normal
operation, including booting. What benchmark or real-work is having
problems here?
> Also based on recent movement of kernfs_rwsem into kernfs_root, do you
> think that the above mentioned mutex and spinlock can be moved to
> kernfs_root as well. Although that change would not help in my current
> case, but it could avoid similar contentions between different users of
> kernfs like cgroup and sysfs
Why would you want to move it if you do not see a measured benefit?
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-04 7:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-03 8:45 [RFC PATCH v2 0/2] " Imran Khan
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 [this message]
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=YdP57ij4JxahpdnC@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=imran.f.khan@oracle.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
Powered by JetHome