[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lf3r7mqr.ffs@tglx>
Date: Mon, 20 Sep 2021 09:02:52 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Huang Ying <ying.huang@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org,
Huang Ying <ying.huang@...el.com>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Yang Shi <shy828301@...il.com>, Zi Yan <ziy@...dia.com>,
Michal Hocko <mhocko@...e.com>, Wei Xu <weixugc@...gle.com>,
Oscar Salvador <osalvador@...e.de>,
David Rientjes <rientjes@...gle.com>,
Dan Williams <dan.j.williams@...el.com>,
David Hildenbrand <david@...hat.com>,
Greg Thelen <gthelen@...gle.com>,
Keith Busch <kbusch@...nel.org>
Subject: Re: [PATCH] mm/migrate: fix CPUHP state to update node demotion order
On Sat, Sep 18 2021 at 10:58, Huang Ying wrote:
> @@ -72,6 +72,7 @@ enum cpuhp_state {
> CPUHP_SLUB_DEAD,
> CPUHP_DEBUG_OBJ_DEAD,
> CPUHP_MM_WRITEBACK_DEAD,
> + CPUHP_MM_DEMOTION_OFFLINE,
Please keep the _DEAD convention in that section. The plugged CPU is
already gone.
> CPUHP_MM_VMSTAT_DEAD,
> CPUHP_SOFTIRQ_DEAD,
> CPUHP_NET_MVNETA_DEAD,
> @@ -240,6 +241,7 @@ enum cpuhp_state {
> CPUHP_AP_BASE_CACHEINFO_ONLINE,
> CPUHP_AP_ONLINE_DYN,
> CPUHP_AP_ONLINE_DYN_END = CPUHP_AP_ONLINE_DYN + 30,
> + CPUHP_AP_MM_DEMOTION_ONLINE,
Are there any ordering requirements of these states vs. other CPU
hotplug states?
If not, then please use the dynamically allocated states.
If so, then please add a comment:
+ /* Must be before CPUHP_XXX and after CPUHP_YYY */
+ CPUHP_MM_DEMOTION_OFFLINE,
Thanks,
tglx
Powered by blists - more mailing lists