From: David Rientjes <rientjes@google.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: akpm@linux-foundation.org, Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
mhocko@kernel.org, vbabka@suse.cz, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] slub: Remove userspace notifier for cache add/remove
Date: Thu, 23 Apr 2020 12:51:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2004231250480.248617@chino.kir.corp.google.com> (raw)
In-Reply-To: <20200423115721.19821-1-mkoutny@suse.com>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
On Thu, 23 Apr 2020, Michal Koutný wrote:
> From: Christoph Lameter <cl@linux.com>
>
> I came across some unnecessary uevents once again which reminded me
> this. The patch seems to be lost in the leaves of the original
> discussion [1], so resending.
>
> [1] https://lore.kernel.org/r/alpine.DEB.2.21.2001281813130.745@www.lameter.com
>
> 8<---
> Kmem caches are internal kernel structures so it is strange that
> userspace notifiers would be needed. And I am not aware of any use
> of these notifiers. These notifiers may just exist because in the
> initial slub release the sysfs code was copied from another
> subsystem.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
> Acked-by: Vlastimil Babka <vbabka@suse.cz>
> Acked-by: Michal Koutný <mkoutny@suse.com>
Acked-by: David Rientjes <rientjes@google.com>
prev parent reply other threads:[~2020-04-23 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 11:57 [PATCH RESEND] slub: Remove userspace notifier for cache add/remove Michal Koutný
2020-04-23 19:51 ` David Rientjes [this message]
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.22.394.2004231250480.248617@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mkoutny@suse.com \
--cc=penberg@kernel.org \
--cc=vbabka@suse.cz \
/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).