From: Tejun Heo <tj@kernel.org>
To: Imran Khan <imran.f.khan@oracle.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 1/2] kernfs: use hashed mutex and spinlock in place of global ones.
Date: Mon, 14 Feb 2022 07:39:17 -1000 [thread overview]
Message-ID: <YgqTxbu2c5yarWMu@slm.duckdns.org> (raw)
In-Reply-To: <d07546ea-0dd3-f795-ee04-e4b40db5354d@oracle.com>
Hello,
On Mon, Feb 14, 2022 at 11:19:38PM +1100, Imran Khan wrote:
> > * How did you come up with the above numbers? Are they based on some
> > experimentation? It'd be nice if the comment explains why the numbers are
> > like that.
> >
>
> I did some testing using different number of CPUs with qemu and the
> above numbers were collected from there. It may not be optimum but this
> is what I could think of while doing those internal tests.
>
> Do you think it may be better to make this configurable via Kconfig.
I think it's good as-is for now and it's super easy and cheap to increase
the hashtable size when some cases see a high contention.
Thanks.
--
tejun
next prev parent reply other threads:[~2022-02-14 17:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-06 1:09 [PATCH v5 0/2] kernfs: use hashed mutex and spinlock in place of global ones Imran Khan
2022-02-06 1:09 ` [PATCH v5 1/2] " Imran Khan
2022-02-08 11:27 ` Greg KH
2022-02-14 12:13 ` Imran Khan
2022-02-08 17:22 ` Tejun Heo
2022-02-14 12:19 ` Imran Khan
2022-02-14 17:39 ` Tejun Heo [this message]
2022-02-06 1:09 ` [PATCH v5 2/2] kernfs: Replace per-fs global rwsem with per-fs hashed rwsem Imran Khan
2022-02-08 18:26 ` Tejun Heo
2022-02-14 12:27 ` 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=YgqTxbu2c5yarWMu@slm.duckdns.org \
--to=tj@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=imran.f.khan@oracle.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).