Re: [RFC PATCH V1 09/13] mm: Add heuristic to calculate target node

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, 19 Mar 2025 19:30:24 +0000
Raghavendra K T <raghavendra.kt@xxxxxxx> wrote:

> One of the key challenges in PTE A bit based scanning is to find right
> target node to promote to.

I have the same problem with the CXL hotpage monitor so very keen to
see solutions to this (though this particular one doesn't work for
me unless A bit scanning is happening as well).

> 
> Here is a simple heuristic based approach:
>    While scanning pages of any mm we also scan toptier pages that belong
> to that mm. We get an insight on the distribution of pages that potentially
> belonging to particular toptier node and also its recent access.
> 
> Current logic walks all the toptier node, and picks the one with highest
> accesses.

Maybe talk through why this heuristic works?  What is the intuition behind it?

I can see that on basis of first touch allocation, we should get a reasonable
number of pages in the node where that CPU doing initialization is. 

Is this relying on some other mechanism to ensure that the pages being touched
are local to the CPUs touching them?

Thanks,

Jonathan


> 
> Signed-off-by: Raghavendra K T <raghavendra.kt@xxxxxxx>
> ---
> PS: There are many potential idea possible here.
> 1. we can do a quick sort on toptier nodes scan and access info
>   and maintain the list of preferred nodes/fallback nodes
>  in case of current target_node is getting filled up
> 
> 2. We can also keep the history of access/scan information from last
> scan used its decayed value to get a stable view etc etc.
> 





[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux