lkml.org 
[lkml]   [2021]   [Sep]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH 1/2] mm/migrate: optimize hotplug-time demotion order updates
From
Date
On 9/21/21 7:36 AM, Huang, Ying wrote:
>> This removes the need for the demotion code to track *any* state. I've
>> attached a totally untested patch to do this.
> Yes. This sounds good. I will try to test this patch on my side.
>
>>From another point of view, we still need to update demotion order upon
> CPU hotplug too, because whether a node has CPU may be changed there.
> And we need a solution for that too.

Just to recap... The reason I sent this series is that there's a known,
detectable regression in a memory hotplug "benchmark". This affects the
5.15 series.

While I agree that we should look into the impact on CPU hotplug, I
think we should probably focus on the *known* memory hotplug issue for 5.15.

\
 
 \ /
  Last update: 2021-09-21 19:02    [W:0.083 / U:0.068 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site