From: Barry Song <baohua@kernel.org>
To: "郑堂权(Blues Zheng)" <zhengtangquan@oppo.com>
Cc: wangzicheng <wangzicheng@honor.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Lei Liu <liulei.rjpt@vivo.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Axel Rasmussen <axelrasmussen@google.com>,
Yuanchu Xie <yuanchu@google.com>, Wei Xu <weixugc@google.com>,
Kairui Song <kasong@tencent.com>, wangtao <tao.wangtao@honor.com>,
liulu 00013167 <liulu.liu@honor.com>
Subject: Re: [PATCH RFC] mm/mglru: lazily activate folios while folios are really mapped
Date: Fri, 3 Apr 2026 06:29:32 +0800 [thread overview]
Message-ID: <CAGsJ_4yjBEj=449YuOerqRN97SH+5ZVM067g=NHdqTEAPT133Q@mail.gmail.com> (raw)
In-Reply-To: <SG2PR02MB5409697C73FDDDC6ADDA33FBDC4CA@SG2PR02MB5409.apcprd02.prod.outlook.com>
On Fri, Mar 20, 2026 at 5:59 PM 郑堂权(Blues Zheng) <zhengtangquan@oppo.com> wrote:
>
> Hi Zicheng,
>
> We ran the same RFC on 6.6, 8 GB, with zstd in our internal whole-system perf model. /proc/vmstat (before → after; % = reduction):
> pgpgin 57807848 55738480 −3.58%
> pgpgout 31585160 26367420 −16.52%
> pswpin 2305528 1534481 −33.44%
> pswpout 6618935 5327316 −19.51%
> workingset_refault_anon 2104047 1356316 −35.54%
> workingset_refault_file 9020966 8407346 −6.80%
> workingset_activate_anon 1196828 412937 −65.50%
> workingset_activate_file 2941357 1468218 −50.08%
> workingset_restore_anon 590337 412322 −30.15%
> workingset_restore_file 1801398 1285060 −28.66%
> workingset_nodereclaim 201014 152864 −23.95%
>
> Here both file and anon refault drop—different from your Android run, likely workload/environment.
Thanks to both Tangquan and Zicheng for the data. I’m guessing the
difference might be related to the readahead and fault_around settings
on low-end phones. Tangquan, would you be willing to share whether you’ve
ever adjusted the readahead window or fault-around pages to make the patch
work better?
I guess this could be helpful in shaping a new version.
Thanks
Barry
next prev parent reply other threads:[~2026-04-02 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-25 22:37 Barry Song
2026-02-26 12:57 ` wangzicheng
2026-02-27 0:15 ` Barry Song
2026-02-28 10:28 ` wangzicheng
2026-03-01 4:16 ` Barry Song
2026-03-19 10:12 ` wangzicheng
2026-03-20 9:59 ` 答复: " 郑堂权(Blues Zheng)
2026-04-02 22:29 ` Barry Song [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-02-25 21:26 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='CAGsJ_4yjBEj=449YuOerqRN97SH+5ZVM067g=NHdqTEAPT133Q@mail.gmail.com' \
--to=baohua@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liulei.rjpt@vivo.com \
--cc=liulu.liu@honor.com \
--cc=surenb@google.com \
--cc=tao.wangtao@honor.com \
--cc=wangzicheng@honor.com \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=yuanchu@google.com \
--cc=zhengtangquan@oppo.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