Re: [RFC PATCH v5 00/10] mm: Hot page tracking and promotion infrastructure

[Bharata B Rao <bharata@amd.com>]

On 24-Feb-26 9:00 PM, Gregory Price wrote:
>>
>> For pghot-default, with target_nid alternating between the available
>> toptier nodes 0 and 1, the numbers catch up with pghot-precise and base
>> NUMAB2 case as seen below:
>> ================================
>> Time in seconds         4337.98
>> Mop/s total             90217.86
>>
>> pgpromote_success       42170085
>> pgpromote_candidate     0
>> pgpromote_candidate_nrl 42171963
>> pgdemote_kswapd         0
>> numa_pte_updates        42338538
>> numa_hint_faults        42185662
>> ================================
>>
> 
> Fascinating! Thank you for the quick follow up.
> 
> I wonder if this was a lucky run, it almost seems *too* perfect.

It consistently performs that way. Here are the numbers from another
run:

================================
Time in seconds         4329.22
Mop/s total             90400.27

pgpromote_success       41967282
pgpromote_candidate     0
pgpromote_candidate_nrl 41968339
pgdemote_kswapd         0
numa_pte_updates        42253854
numa_hint_faults        42019449
================================

grep -E "pgpromote|pgdemote" /sys/devices/system/node/node0/vmstat
pgpromote_success 20996597
pgpromote_candidate 0
pgpromote_candidate_nrl 41968339 (*)
pgdemote_kswapd 0
pgdemote_direct 0
pgdemote_khugepaged 0
pgdemote_proactive 0

grep -E "pgpromote|pgdemote" /sys/devices/system/node/node1/vmstat
pgpromote_success 20970685
pgpromote_candidate 0
pgpromote_candidate_nrl 0
pgdemote_kswapd 0
pgdemote_direct 0
pgdemote_khugepaged 0
pgdemote_proactive 0


(*) The round-robin b/n nodes 0 and 1 happens after this metric is
attributed to the original default target_nid. Hence nrl metric
gets populated for node 0 only.