[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86383ac9-e5f2-1a2e-dd19-02e39714a3fd@intel.com>
Date: Tue, 8 Mar 2022 09:07:20 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Oscar Salvador <osalvador@...e.de>,
"Huang, Ying" <ying.huang@...el.com>
Cc: Abhishek Goel <huntbag@...ux.vnet.ibm.com>,
Dave Hansen <dave.hansen@...ux.intel.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Zi Yan <ziy@...dia.com>,
David Hildenbrand <david@...hat.com>,
Yang Shi <yang.shi@...ux.alibaba.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH -V11 2/9] mm/migrate: update node demotion order on
hotplug events
On 3/8/22 02:27, Oscar Salvador wrote:
> @@ -2043,7 +2044,12 @@ static void __init init_cpu_node_state(void)
> static int vmstat_cpu_online(unsigned int cpu)
> {
> refresh_zone_stat_thresholds();
> - node_set_state(cpu_to_node(cpu), N_CPU);
> +
> + if (!node_state(cpu_to_node(cpu), N_CPU)) {
> + node_set_state(cpu_to_node(cpu), N_CPU);
> + set_migration_target_nodes();
> + }
> +
> return 0;
> }
>
> @@ -2066,6 +2072,8 @@ static int vmstat_cpu_dead(unsigned int cpu)
> return 0;
>
> node_clear_state(node, N_CPU);
> + set_migration_target_nodes();
> +
> return 0;
> }
Yeah, those callbacks do look like they're reinventing the wheel. This
is a much more direct way of doing it.
Powered by blists - more mailing lists