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: Mon, 3 Jan 2022 10:54:50 +0100 [thread overview]
Message-ID: <YdLH6qQNxa11YmRO@kroah.com> (raw)
In-Reply-To: <20220103084544.1109829-2-imran.f.khan@oracle.com>
On Mon, Jan 03, 2022 at 07:45:43PM +1100, Imran Khan wrote:
> diff --git a/include/linux/kernfs.h b/include/linux/kernfs.h
> index 861c4f0f8a29..5ed4c9ed39af 100644
> --- a/include/linux/kernfs.h
> +++ b/include/linux/kernfs.h
> @@ -164,6 +164,8 @@ struct kernfs_node {
> unsigned short flags;
> umode_t mode;
> struct kernfs_iattrs *iattr;
> + spinlock_t kernfs_open_node_lock;
> + struct mutex kernfs_open_file_mutex;
Did you just blow up the memory requirements of a system with lots of
kobjects created?
We used to be able to support tens of thousands of scsi devices in a
32bit kernel, with this change, what is the memory difference that just
happened?
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.
thanks,
greg k-h
next prev parent reply other threads:[~2022-01-03 9:55 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 [this message]
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=YdLH6qQNxa11YmRO@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