From: sashiko-bot@kernel.org
To: "Barry Song (Xiaomi)" <baohua@kernel.org>, akpm@linux-foundation.org
Cc: axelrasmussen@google.com, baolin.wang@linux.alibaba.com,
baoquan.he@linux.dev, hannes@cmpxchg.org, hui.zhu@linux.dev,
kasong@tencent.com, kunwu.chan@gmail.com, liam@infradead.org,
lianux.mm@gmail.com, linux-mm@kvack.org,
liuxiang.277@bytedance.com, lyugaofei@xiaomi.com,
mhocko@kernel.org, mhocko@suse.com, qi.zheng@linux.dev,
ridong.chen@linux.dev, rppt@kernel.org, ryncsn@gmail.com,
shakeel.butt@linux.dev, surenb@google.com, wangzicheng@honor.com,
weixugc@google.com, yuanchu@google.com, zhangbo56@xiaomi.com,
zhuhui@kylinos.cn, sidchintamaneni@gmail.com
Subject: Re: [PATCH v7 05/16] mm/mglru: skip zones above reclaim_idx instead of rotating them
Date: Thu, 12 Nov 2026 05:01:00 +0000 [thread overview]
Message-ID: <sashiko-outbox-210413@kernel.org> (raw)
In-Reply-To: <20261111232603.9934-6-baohua@kernel.org>
Thank you for your contribution! Sashiko AI review found 1 potential
issue to consider:
- [High] mm/mglru: pinned min_seq in try_to_inc_min_seq() stalls aging
--
commit a9558af5b6eefdf9bb9a64058218b290ef8ecc66
Author: Kairui Song <kasong@tencent.com>
mm/mglru: skip zones above reclaim_idx instead of rotating them
This commit restricts scan_folios() and lruvec_populated_min_seq() to zones up
to sc->reclaim_idx instead of scanning and rotating folios in higher zones.
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 51c2ee66b3ee8..273aa8c56bec8 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -3992,7 +3992,7 @@ static bool inc_min_seq(struct lruvec *lruvec, int type, int swappiness)
>
> /* Similar to lruvec_evictable_size, return the oldest populated seq of the type */
> static unsigned long lruvec_populated_min_seq(struct lruvec *lruvec, int type,
> - unsigned long max_seq)
> + int zone_limit, unsigned long max_seq)
> {
> int gen, zone;
> unsigned long min_seq;
> @@ -4003,7 +4003,7 @@ static unsigned long lruvec_populated_min_seq(struct lruvec *lruvec, int type,
> min_seq = READ_ONCE(lrugen->min_seq[type]);
> while (min_seq <= max_seq) {
> gen = lru_gen_from_seq(min_seq);
> - for (zone = 0; zone < MAX_NR_ZONES; zone++) {
> + for (zone = 0; zone < zone_limit; zone++) {
> if (!list_empty(&lrugen->folios[gen][type][zone]))
> return min_seq;
> }
> @@ -4026,7 +4026,7 @@ static void try_to_inc_min_seq(struct lruvec *lruvec, int swappiness)
> /* Requires at least MIN_NR_GENS gens for basic functionality */
> seq = lrugen->max_seq - MIN_NR_GENS;
> for_each_evictable_type(type, swappiness) {
> - min_seq[type] = lruvec_populated_min_seq(lruvec, type, seq + 1);
> + min_seq[type] = lruvec_populated_min_seq(lruvec, type, MAX_NR_ZONES, seq + 1);
> if (min_seq[type] > lrugen->min_seq[type])
> seq_inc_flag = true;
> }
[ ... ]
> @@ -4780,24 +4773,22 @@ static int scan_folios(unsigned long nr_to_scan, struct lruvec *lruvec,
> * when under pressure to respect swappiness more and reduce IO cost.
> */
> if (sc->priority == DEF_PRIORITY)
> - min_seq = lrugen->min_seq[type];
> + seq = lrugen->min_seq[type];
> else
> - min_seq = lruvec_populated_min_seq(lruvec, type, lrugen->max_seq);
> + seq = lrugen->max_seq;
>
> - gen = lru_gen_from_seq(min_seq);
> + seq = lruvec_populated_min_seq(lruvec, type, sc->reclaim_idx + 1, seq);
> + gen = lru_gen_from_seq(seq);
> max_gen = lru_gen_from_seq(max_seq);
>
> - for (i = MAX_NR_ZONES; i > 0; i--) {
> + /* Scan eligible zones in descending order. */
> + for (zone_idx = sc->reclaim_idx; zone_idx >= 0; zone_idx--) {
[Severity: High]
As reported by KunWu Chan on RFC v5 [1], does skipping zones above
sc->reclaim_idx in scan_folios() while try_to_inc_min_seq() still checks all
MAX_NR_ZONES stall aging during zone-constrained reclaim (for example,
GFP_DMA32 reclaim when ZONE_NORMAL is populated)?
When an lruvec has MAX_NR_GENS (4) generations, lrugen->min_seq[type] starts
at max_seq - 3. Because scan_folios() no longer rotates folios in zones above
sc->reclaim_idx, any folios in those zones keep try_to_inc_min_seq() from
advancing lrugen->min_seq[type] once eligible zones are drained.
In should_run_aging():
mm/vmscan.c:should_run_aging() {
...
if (evictable_min_seq(min_seq, swappiness) + MIN_NR_GENS > max_seq)
return true;
/* try to avoid aging, do gentle reclaim at the default priority */
if (sc->priority == DEF_PRIORITY)
return false;
/* better to run aging even though eviction is still possible */
return evictable_min_seq(min_seq, swappiness) + MIN_NR_GENS == max_seq;
}
With min_seq pinned at max_seq - 3, evictable_min_seq() + MIN_NR_GENS never
reaches max_seq, so should_run_aging() returns false and scan_folios() drains
eligible zones down to the youngest generation max_seq where sort_folio()
disables tier protection and workingset promotion (min_gen == max_gen).
Even with the follow-up commits in this series (commit "mm/mglru: Run aging
when pages are rare outside the youngest gen", commit "mm/mglru: Run aging
when one type has no populatable folios", and commit "mm/mglru: Restrict
eviction accounting to eligible zones"), at priorities above DEF_PRIORITY / 2
scan_folios() caps seq at max_seq - 1 and evict_folio_lists() returns 0 once
older generations are empty in eligible zones, causing try_to_shrink_lruvec()
to break out before calling should_run_aging() until priority drops to
DEF_PRIORITY / 2 and scans max_seq without tier protection.
[1] https://lore.kernel.org/r/CAN_Opa-AScm9=EeXO_Uy8VjbQ=bqY9P++rFP8H1RhUB4dOt6xw@mail.gmail.com
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261111232603.9934-1-baohua@kernel.org?part=5
next prev parent reply other threads:[~2026-11-12 5:01 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 23:25 [PATCH v7 00/16] mm: mglru: fix swappiness behavior Barry Song (Xiaomi)
2026-11-11 23:25 ` [PATCH v7 01/16] mm/mglru: report evictable sizes per type Barry Song (Xiaomi)
2026-11-11 23:25 ` [PATCH v7 02/16] mm/mglru: extract lruvec_populated_min_seq() helper Barry Song (Xiaomi)
2026-11-12 5:00 ` sashiko-bot
2026-11-11 23:25 ` [PATCH v7 03/16] mm/mglru: reclaim from the oldest populated gen Barry Song (Xiaomi)
2026-11-12 5:00 ` sashiko-bot
2026-11-11 23:25 ` [PATCH v7 04/16] mm/mglru: lift the forced protection of reclaimer Barry Song (Xiaomi)
2026-11-12 5:00 ` sashiko-bot
2026-11-11 23:25 ` [PATCH v7 05/16] mm/mglru: skip zones above reclaim_idx instead of rotating them Barry Song (Xiaomi)
2026-11-12 5:01 ` sashiko-bot [this message]
2026-11-11 23:25 ` [PATCH v7 06/16] mm/mglru: return for unavailable anon reclaim earlier Barry Song (Xiaomi)
2026-11-11 23:25 ` [PATCH v7 07/16] mm/mglru: balance anon and file scan budget by refault rate Barry Song (Xiaomi)
2026-11-12 5:01 ` sashiko-bot
2026-11-11 23:25 ` [PATCH v7 08/16] mm/mglru: lift youngest gen protection for higher priority Barry Song (Xiaomi)
2026-11-11 23:25 ` [PATCH v7 09/16] mm/mglru: Avoid placing rejected folios below populated gen Barry Song (Xiaomi)
2026-11-11 23:25 ` [PATCH v7 10/16] mm/mglru: Run aging when pages are rare outside the youngest gen Barry Song (Xiaomi)
2026-11-12 5:01 ` sashiko-bot
2026-11-11 23:25 ` [PATCH v7 11/16] mm/mglru: Run aging when one type has no populatable folios Barry Song (Xiaomi)
2026-11-12 5:01 ` sashiko-bot
2026-11-11 23:25 ` [PATCH v7 12/16] mm/mglru: Restrict eviction accounting to eligible zones Barry Song (Xiaomi)
2026-11-12 5:01 ` sashiko-bot
2026-11-11 23:26 ` [PATCH v7 13/16] mm/mglru: Reduce LRU lock contention by shrinking folio batches in inc_min_seq Barry Song (Xiaomi)
2026-11-11 23:26 ` [PATCH v7 14/16] mm/mglru: Avoid prolonged anon reclaim with swappiness=200 Barry Song (Xiaomi)
2026-11-12 5:01 ` sashiko-bot
2026-11-11 23:26 ` [PATCH v7 15/16] mm/mglru: Make swappiness=1 file reclaim more aggressive Barry Song (Xiaomi)
2026-11-12 5:01 ` sashiko-bot
2026-11-11 23:26 ` [PATCH v7 16/16] mm/mglru: Avoid scan anon while swapcache is low for GFP_NOIO allocation Barry Song (Xiaomi)
2026-11-12 5:01 ` sashiko-bot
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=sashiko-outbox-210413@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=baoquan.he@linux.dev \
--cc=hannes@cmpxchg.org \
--cc=hui.zhu@linux.dev \
--cc=kasong@tencent.com \
--cc=kunwu.chan@gmail.com \
--cc=liam@infradead.org \
--cc=lianux.mm@gmail.com \
--cc=linux-mm@kvack.org \
--cc=liuxiang.277@bytedance.com \
--cc=lyugaofei@xiaomi.com \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=qi.zheng@linux.dev \
--cc=ridong.chen@linux.dev \
--cc=rppt@kernel.org \
--cc=ryncsn@gmail.com \
--cc=sashiko-reviews@lists.linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=sidchintamaneni@gmail.com \
--cc=surenb@google.com \
--cc=wangzicheng@honor.com \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=zhangbo56@xiaomi.com \
--cc=zhuhui@kylinos.cn \
/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