Re: [PATCH -next v2] mm: vmscan: correct nr_requested tracing in scan_folios

[Lance Yang]

On 2025/12/4 20:23, Chen Ridong wrote:
> From: Chen Ridong <chenridong@xxxxxxxxxx>
>
> When enabling vmscan tracing, it is observed that nr_requested is always
> 4096, which is confusing.
>
>          mm_vmscan_lru_isolate: classzone=3 order=0 nr_requested=4096 ...
>          mm_vmscan_lru_isolate: classzone=3 order=0 nr_requested=4096 ...
>          mm_vmscan_lru_isolate: classzone=3 order=0 nr_requested=4096 ...
>          mm_vmscan_lru_isolate: classzone=3 order=0 nr_requested=4096 ...
>          mm_vmscan_lru_isolate: classzone=3 order=0 nr_requested=4096 ...
>          mm_vmscan_lru_isolate: classzone=3 order=0 nr_requested=4096 ...
>          mm_vmscan_lru_isolate: classzone=3 order=0 nr_requested=4096 ...
>
> This is because it prints MAX_LRU_BATCH, which is meaningless as it's a
> constant. To fix this, modify it to print capped valued.
>
> Fixes: 8c2214fc9a47 ("mm: multi-gen LRU: reuse some legacy trace events")
> Signed-off-by: Chen Ridong <chenridong@xxxxxxxxxx>
> ---

LGTM, feel free to add:

Reviewed-by: Lance Yang <lance.yang@xxxxxxxxx>