From: "David Hildenbrand (Red Hat)" <david@kernel.org>
To: Chen Ridong <chenridong@huaweicloud.com>,
akpm@linux-foundation.org, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, hannes@cmpxchg.org,
mhocko@kernel.org, zhengqi.arch@bytedance.com,
shakeel.butt@linux.dev, lorenzo.stoakes@oracle.com,
yuzhao@google.com, jaewon31.kim@samsung.com, ioworker0@gmail.com
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
lujialin4@huawei.com, chenridong@huawei.com
Subject: Re: [PATCH -next v2] mm: vmscan: correct nr_requested tracing in scan_folios
Date: Thu, 4 Dec 2025 13:42:18 +0100 [thread overview]
Message-ID: <308c809e-160a-4829-a8b9-9c7682fcd251@kernel.org> (raw)
In-Reply-To: <20251204122355.1822919-1-chenridong@huaweicloud.com>
On 12/4/25 13:23, Chen Ridong wrote:
> From: Chen Ridong <chenridong@huawei.com>
>
> 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@huawei.com>
> ---
> mm/vmscan.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 584f41eb4c14..a0a74cac947b 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -4404,7 +4404,8 @@ static int scan_folios(unsigned long nr_to_scan, struct lruvec *lruvec,
> int scanned = 0;
> int isolated = 0;
> int skipped = 0;
> - int remaining = min(nr_to_scan, MAX_LRU_BATCH);
> + int scan_batch = min(nr_to_scan, MAX_LRU_BATCH);
> + int remaining = scan_batch;
> struct lru_gen_folio *lrugen = &lruvec->lrugen;
> struct mem_cgroup *memcg = lruvec_memcg(lruvec);
>
> @@ -4464,7 +4465,7 @@ static int scan_folios(unsigned long nr_to_scan, struct lruvec *lruvec,
> count_memcg_events(memcg, item, isolated);
> count_memcg_events(memcg, PGREFILL, sorted);
> __count_vm_events(PGSCAN_ANON + type, isolated);
> - trace_mm_vmscan_lru_isolate(sc->reclaim_idx, sc->order, MAX_LRU_BATCH,
> + trace_mm_vmscan_lru_isolate(sc->reclaim_idx, sc->order, scan_batch,
> scanned, skipped, isolated,
> type ? LRU_INACTIVE_FILE : LRU_INACTIVE_ANON);
> if (type == LRU_GEN_FILE)
Acked-by: David Hildenbrand (Red Hat) <david@kernel.org>
--
Cheers
David
next prev parent reply other threads:[~2025-12-04 12:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-04 12:23 Chen Ridong
2025-12-04 12:42 ` David Hildenbrand (Red Hat) [this message]
2025-12-04 13:35 ` Lance Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=308c809e-160a-4829-a8b9-9c7682fcd251@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=ioworker0@gmail.com \
--cc=jaewon31.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lujialin4@huawei.com \
--cc=mhocko@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=yuzhao@google.com \
--cc=zhengqi.arch@bytedance.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox