From: Christoph Lameter <cl@linux.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Qian Cai <cai@redhat.com>, David Hildenbrand <david@redhat.com>,
Michal Hocko <mhocko@kernel.org>
Subject: Re: [RFC 0/3] mm, slab, slub: remove cpu and memory hotplug locks
Date: Wed, 6 Jan 2021 19:09:25 +0000 (UTC) [thread overview]
Message-ID: <alpine.DEB.2.22.394.2101061907330.2652@www.lameter.com> (raw)
In-Reply-To: <20210106174029.12654-1-vbabka@suse.cz>
On Wed, 6 Jan 2021, Vlastimil Babka wrote:
> rather accept some wasted memory in scenarios that should be rare anyway (full
> memory hot remove), as we do the same in other contexts already. It's all RFC
> for now, as I might have missed some reason why it's not safe.
Looks good to me. My only concern is the kernel that has hotplug disabled.
Current code allows the online/offline checks to be optimized away.
Can this patch be enhanced to do the same?
next prev parent reply other threads:[~2021-01-06 19:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 17:40 [RFC 0/3] mm, slab, slub: remove cpu and memory hotplug locks Vlastimil Babka
2021-01-06 17:40 ` [RFC 1/3] mm, slab, slub: stop taking memory hotplug lock Vlastimil Babka
2021-01-06 17:40 ` [RFC 2/3] mm, slab, slub: stop taking cpu " Vlastimil Babka
2021-01-06 17:40 ` [RFC 3/3] mm, slub: stop freeing kmem_cache_node structures on node offline Vlastimil Babka
2021-01-06 19:09 ` Christoph Lameter [this message]
2021-01-11 17:55 ` [RFC 0/3] mm, slab, slub: remove cpu and memory hotplug locks 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.22.394.2101061907330.2652@www.lameter.com \
--to=cl@linux.com \
--cc=cai@redhat.com \
--cc=david@redhat.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
/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).