[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f5edb9dc-8b25-47c2-9905-09e88e41861b@intel.com>
Date: Wed, 23 Feb 2022 16:05:59 -0800
From: Dave Hansen <dave.hansen@...el.com>
To: Abhishek Goel <huntbag@...ux.vnet.ibm.com>,
Dave Hansen <dave.hansen@...ux.intel.com>
Cc: 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>,
Huang Ying <ying.huang@...el.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH -V11 2/9] mm/migrate: update node demotion order on
hotplug events
On 2/23/22 15:02, Abhishek Goel wrote:
> If needed, I will provide experiment results and traces that were used
> to conclude this.
It would be great if you can provide some more info. Even just a CPU
time profile would be helpful.
It would also be great to understand more about what "hotplug on power
systems" actually means. Is this a synthetic benchmark, or are actual
end-users running into this issue? Are entire nodes of CPUs going
offline? Or is this just doing an offline/online of CPU 22 in a 100-CPU
NUMA node?
Powered by blists - more mailing lists