From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: "Barry Song (Xiaomi)" <baohua@kernel.org>,
akpm@linux-foundation.org, linux-mm@kvack.org
Cc: hannes@cmpxchg.org, david@kernel.org, mhocko@kernel.org,
qi.zheng@linux.dev, shakeel.butt@linux.dev, ljs@kernel.org,
kasong@tencent.com, axelrasmussen@google.com, yuanchu@google.com,
weixugc@google.com, linux-kernel@vger.kernel.org,
lyugaofei@xiaomi.com, stevensd@chromium.org
Subject: Re: [RFC PATCH v2 5/5] mm: mglru: run aging if the preferred type has no folios in reclaimable gens
Date: Fri, 31 Jul 2026 15:26:50 +0800 [thread overview]
Message-ID: <3869ea1a-23e4-4b82-bebc-8cf1ae282fc5@linux.alibaba.com> (raw)
In-Reply-To: <20260726122123.7614-6-baohua@kernel.org>
On 7/26/26 8:21 PM, Barry Song (Xiaomi) wrote:
> Respect the type selected by positive_ctrl_err(). If there are no
> reclaimable gens left for that type, run aging.
>
> Signed-off-by: Barry Song (Xiaomi) <baohua@kernel.org>
> ---
> mm/vmscan.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/mm/vmscan.c b/mm/vmscan.c
> index 7c13dedb0b1f..d63322cdb1bc 100644
> --- a/mm/vmscan.c
> +++ b/mm/vmscan.c
> @@ -4996,6 +4996,10 @@ static bool should_run_aging(struct lruvec *lruvec, unsigned long max_seq,
> if (evictable_min_seq(min_seq, swappiness) + MIN_NR_GENS > max_seq)
> return true;
>
> + /* run aging if the preferred type is exhausted */
> + if (min_seq[type] + 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;
Looks reasonable to me.
Additionally, for sc->priority > DEF_PRIORITY, is there the same check
logic for the scan type?
if (min_seq[type] + MIN_NR_GENS == max_seq)
return true;
next prev parent reply other threads:[~2026-07-31 7:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-26 12:21 [RFC PATCH v2 0/5] mm: mglru: fix swappiness behavior Barry Song (Xiaomi)
2026-07-26 12:21 ` [RFC PATCH v2 1/5] mm: mglru: avoid scanning empty generations in scan_folios() Barry Song (Xiaomi)
2026-07-27 23:18 ` Barry Song
2026-07-30 6:41 ` Lian Wang
2026-07-30 7:05 ` Barry Song
2026-07-30 7:21 ` Lian Wang
2026-07-26 12:21 ` [RFC PATCH v2 2/5] mm: mglru: only fall back when reclaim is running at high priority Barry Song (Xiaomi)
2026-07-26 22:08 ` Barry Song
2026-07-26 12:21 ` [RFC PATCH v2 3/5] mm: mglru: prevent min_seq[type] from pointing to an empty generation Barry Song (Xiaomi)
2026-07-26 12:21 ` [RFC PATCH v2 4/5] mm: mglru: run aging when pages are severely imbalanced across gens Barry Song (Xiaomi)
2026-07-28 3:46 ` Zicheng Wang
2026-07-28 11:20 ` Barry Song
2026-07-28 12:27 ` Zicheng Wang
2026-07-29 22:36 ` Barry Song
2026-07-30 11:38 ` wangzicheng
2026-07-30 12:22 ` Kairui Song
2026-07-26 12:21 ` [RFC PATCH v2 5/5] mm: mglru: run aging if the preferred type has no folios in reclaimable gens Barry Song (Xiaomi)
2026-07-31 7:26 ` Baolin Wang [this message]
2026-07-31 9:01 ` Barry Song
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=3869ea1a-23e4-4b82-bebc-8cf1ae282fc5@linux.alibaba.com \
--to=baolin.wang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=lyugaofei@xiaomi.com \
--cc=mhocko@kernel.org \
--cc=qi.zheng@linux.dev \
--cc=shakeel.butt@linux.dev \
--cc=stevensd@chromium.org \
--cc=weixugc@google.com \
--cc=yuanchu@google.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
all inboxes | Powered by JetHome®