The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: "Barry Song (Xiaomi)" <baohua@kernel.org>,
	akpm@linux-foundation.org, linux-mm@kvack.org
Cc: axelrasmussen@google.com, baoquan.he@linux.dev,
	chenridong@xiaomi.com, david@kernel.org, hannes@cmpxchg.org,
	kasong@tencent.com, lianux.mm@gmail.com,
	linux-kernel@vger.kernel.org, ljs@kernel.org,
	lyugaofei@xiaomi.com, mhocko@kernel.org, qi.zheng@linux.dev,
	shakeel.butt@linux.dev, stevensd@chromium.org,
	wangzicheng@honor.com, weixugc@google.com, yuanchu@google.com
Subject: Re: [PATCH 0/3] mm/mglru: clean up isolate_folios and scan_folios for readability and clarity
Date: Mon, 24 Aug 2026 15:22:13 +0800	[thread overview]
Message-ID: <7e897a4e-2075-485a-8cc5-5bb928fba437@linux.alibaba.com> (raw)
In-Reply-To: <20260820045603.68809-1-baohua@kernel.org>



On 8/20/26 12:56 PM, Barry Song (Xiaomi) wrote:
> This is a cleanup series split out from the MGLRU swappiness series [1],
> with the cleanup changes separated to make them easier to review.
> 
> Right now, isolate_folios() is quite difficult to follow:
> 
> 1. It uses for_each_evictable_type(i, swappiness) to iterate over the
> types, but i is not actually used as the type within the loop body.
> 
> 2. It uses scanned == 0 to detect whether the current reclaim type is
> exhausted, but this is not an accurate indication.
> 
> 3. It has an internal retry when no folios can be isolated after scanning
> some folios, but the retry is implemented in a way nobody can understand.
> 
> This patchset makes these behaviors explicit and much easier to follow.
> 
> Run kernel builds for several rounds in a 1 GB memcg and take the
> average build time. The patchset shows almost no performance impact,
> with a very small improvement that could simply be noise:

Just FYI:

I tested this patchset with a 3G memcg limit and a 10G zram device, 
running 'make -j32' to build kernel on my 32-core Arm machines, and got 
some performance improvement for ths sys time:
	w/o patch	w/patch
sys	1845s		1570s

>                  w/o patch   w/patch      Delta
> 
> real             109.149    108.990     -0.15%
> sys              223.213    222.592     -0.28%
> 
> pgscan_file      498,208    486,994     -2.25%
> refault_file     262,696    254,688     -3.05%
> 
> Thanks very much to Baolin and Lian for their previous reviews of the
> original RFC patchset for this part.
> 
> [1] https://lore.kernel.org/linux-mm/20260812121658.69965-1-baohua@kernel.org/
> 
> Barry Song (Xiaomi) (2):
>    mm/mglru: improve scan_folios() exhaustion detection
>    mm/mglru: retry the same type once if isolation fails due to races
> 
> Ridong Chen (1):
>    mm/mglru: improve readability of isolate_folios()
> 
>   mm/vmscan.c | 78 ++++++++++++++++++++++++++++++++++++-----------------
>   1 file changed, 54 insertions(+), 24 deletions(-)
> 


  parent reply	other threads:[~2026-08-24  7:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20  4:56 [PATCH 0/3] mm/mglru: clean up isolate_folios and scan_folios for readability and clarity Barry Song (Xiaomi)
2026-08-20  4:56 ` [PATCH 1/3] mm/mglru: improve readability of isolate_folios() Barry Song (Xiaomi)
2026-08-20  9:02   ` Baolin Wang
2026-08-20  9:22   ` Kairui Song
2026-08-20  4:56 ` [PATCH 2/3] mm/mglru: improve scan_folios() exhaustion detection Barry Song (Xiaomi)
2026-08-21  1:44   ` Ridong Chen
2026-08-24  6:47   ` Baolin Wang
2026-08-20  4:56 ` [PATCH 3/3] mm/mglru: retry the same type once if isolation fails due to races Barry Song (Xiaomi)
2026-08-21  1:45   ` Ridong Chen
2026-08-24  7:14   ` Baolin Wang
2026-08-20  7:56 ` [PATCH 0/3] mm/mglru: clean up isolate_folios and scan_folios for readability and clarity Lian Wang (ProcessMission)
2026-08-24  7:22 ` Baolin Wang [this message]
2026-08-24 11:05   ` Kairui 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=7e897a4e-2075-485a-8cc5-5bb928fba437@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=axelrasmussen@google.com \
    --cc=baohua@kernel.org \
    --cc=baoquan.he@linux.dev \
    --cc=chenridong@xiaomi.com \
    --cc=david@kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kasong@tencent.com \
    --cc=lianux.mm@gmail.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=wangzicheng@honor.com \
    --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