From: Christopher Lameter <cl@linux.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-mm@kvack.org
Subject: Re: SLUB: purpose of sysfs events on cache creation/removal
Date: Tue, 26 Nov 2019 16:32:56 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.21.1911261632030.9857@www.lameter.com> (raw)
In-Reply-To: <20191126121901.GE20912@dhcp22.suse.cz>
On Tue, 26 Nov 2019, Michal Hocko wrote:
> Hi,
> I have just learnt about KOBJ_{ADD,REMOVE} sysfs events triggered on
> kmem cache creation/removal when SLUB is configured. This functionality
> goes all the way down to initial SLUB merge. I do not see any references
> in the Documentation explaining what those events are used for and
> whether there are any real users.
>
> Could you shed some more light into this?
I have no idea about what this is. There have been many people who
reworked the sysfs support and this has been the cause for a lot of
breakage over the years.
next prev parent reply other threads:[~2019-11-26 16:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 12:19 SLUB: purpose of sysfs events on cache creation/removal Michal Hocko
2019-11-26 16:32 ` Christopher Lameter [this message]
2019-11-26 16:54 ` Michal Hocko
2019-11-27 15:40 ` Christopher Lameter
2019-11-27 16:24 ` Michal Hocko
2019-11-27 16:26 ` Christopher Lameter
2019-11-27 17:43 ` Michal Hocko
2019-12-04 13:28 ` Michal Hocko
2019-12-04 15:25 ` Christopher Lameter
2019-12-04 15:32 ` Michal Hocko
2019-12-04 16:53 ` Christopher Lameter
2019-12-04 17:32 ` Michal Hocko
2020-01-06 11:57 ` Michal Hocko
2020-01-06 15:51 ` Christopher Lameter
2020-01-09 14:52 ` Michal Hocko
2020-01-09 19:44 ` Andrew Morton
2020-01-09 20:13 ` Michal Hocko
2020-01-09 20:15 ` Michal Hocko
2020-01-17 17:13 ` Michal Koutný
2020-01-19 0:15 ` Andrew Morton
2020-01-27 17:33 ` Michal Koutný
2020-01-27 23:04 ` Christopher Lameter
2020-01-28 8:51 ` Michal Koutný
2020-01-28 18:13 ` Christopher Lameter
2020-01-30 13:16 ` Vlastimil Babka
2020-01-09 14:07 ` Vlastimil Babka
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=alpine.DEB.2.21.1911261632030.9857@www.lameter.com \
--to=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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).