[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220201024238.ihq477dgayy6oxeg@master>
Date: Tue, 1 Feb 2022 02:42:38 +0000
From: Wei Yang <richard.weiyang@...il.com>
To: Michal Hocko <mhocko@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org,
LKML <linux-kernel@...r.kernel.org>,
David Hildenbrand <david@...hat.com>,
Alexey Makhalov <amakhalov@...are.com>,
Dennis Zhou <dennis@...nel.org>,
Eric Dumazet <eric.dumazet@...il.com>,
Oscar Salvador <osalvador@...e.de>, Tejun Heo <tj@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Nico Pache <npache@...hat.com>,
Wei Yang <richard.weiyang@...il.com>,
Rafael Aquini <raquini@...hat.com>,
Michal Hocko <mhocko@...e.com>
Subject: Re: [PATCH 4/6] mm, memory_hotplug: reorganize new pgdat
initialization
On Thu, Jan 27, 2022 at 09:53:03AM +0100, Michal Hocko wrote:
>From: Michal Hocko <mhocko@...e.com>
>
>When a !node_online node is brought up it needs a hotplug specific
>initialization because the node could be either uninitialized yet or it
>could have been recycled after previous hotremove. hotadd_init_pgdat is
>responsible for that.
>
>Internal pgdat state is initialized at two places currently
> - hotadd_init_pgdat
> - free_area_init_core_hotplug
>There is no real clear cut what should go where but this patch's chosen to
>move the whole internal state initialization into free_area_init_core_hotplug.
>hotadd_init_pgdat is still responsible to pull all the parts together -
>most notably to initialize zonelists because those depend on the overall topology.
>
>This patch doesn't introduce any functional change.
>
>Acked-by: Rafael Aquini <raquini@...hat.com>
>Signed-off-by: Michal Hocko <mhocko@...e.com>
Reviewed-by: Wei Yang <richard.weiyang@...il.com>
--
Wei Yang
Help you, Help me
Powered by blists - more mailing lists