[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7f053290-6b9a-4d18-936e-0f28006c79c3@kernel.org>
Date: Tue, 6 Jan 2026 16:24:21 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Gregory Price <gourry@...rry.net>, linux-mm@...ck.org
Cc: linux-kernel@...r.kernel.org, kernel-team@...a.com, osalvador@...e.de,
gregkh@...uxfoundation.org, rafael@...nel.org, dakr@...nel.org,
akpm@...ux-foundation.org, lorenzo.stoakes@...cle.com,
Liam.Howlett@...cle.com, vbabka@...e.cz, rppt@...nel.org, surenb@...gle.com,
mhocko@...e.com, hare@...e.de
Subject: Re: [RFC PATCH] memory,memory_hotplug: allow restricting memory
blocks to zone movable
> +/*
> + * Restrict hotplugged memory blocks to ZONE_MOVABLE only.
> + *
> + * During offlining of hotplugged memory which was originally onlined
> + * as ZONE_MOVABLE, userland services may detect blocks going offline
> + * and automatically re-online them into ZONE_NORMAL or lower. When
> + * this happens it may become permanently incapable of being removed.
If it's really only that, we could also look into simply making a
re-online without a specific mode ("online") to use the previous mode.
We could glue that to the "contig-zones" policy only, to not affect
"auto-movable".
That is, remember the zone to which it was previously onlined, and then
simply re-online to that one.
--
Cheers
David
Powered by blists - more mailing lists