From: Zhongkun He <hezhongkun.hzk@bytedance.com>
To: Muchun Song <muchun.song@linux.dev>
Cc: akpm@linux-foundation.org, hannes@cmpxchg.org, mhocko@suse.com,
yosry.ahmed@linux.dev, yuzhao@google.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH V4 3/4] mm: add max swappiness arg to lru_gen for anonymous memory only
Date: Tue, 22 Apr 2025 14:18:10 +0800 [thread overview]
Message-ID: <CACSyD1MCfAAJ5R0y3Kn5u_a7RyhgZhiBwCF14uEKGAzs-7BbMQ@mail.gmail.com> (raw)
In-Reply-To: <DB64B965-2E54-401E-86F9-8F79C50B21C9@linux.dev>
On Mon, Apr 21, 2025 at 5:36 PM Muchun Song <muchun.song@linux.dev> wrote:
>
>
>
> > On Apr 21, 2025, at 17:13, Zhongkun He <hezhongkun.hzk@bytedance.com> wrote:
> >
> > The MGLRU already supports reclaiming only from anonymous memory
> > via the /sys/kernel/debug/lru_gen interface. Now, memory.reclaim
> > also supports the swappiness=max parameter to enable reclaiming
> > solely from anonymous memory. To unify the semantics of proactive
> > reclaiming from anonymous folios, the max parameter is introduced.
> >
> > Signed-off-by: Zhongkun He <hezhongkun.hzk@bytedance.com>
>
> Acked-by: Muchun Song <muchun.song@linux.dev>
>
Thanks.
> Thanks.
>
next prev parent reply other threads:[~2025-04-22 6:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 9:13 [PATCH V4 0/4] add max arg to swappiness in memory.reclaim and lru_gen Zhongkun He
2025-04-21 9:13 ` [PATCH V4 1/4] mm: add swappiness=max arg to memory.reclaim for only anon reclaim Zhongkun He
2025-04-21 9:34 ` Muchun Song
2025-04-22 6:16 ` [External] " Zhongkun He
2025-04-21 9:13 ` [PATCH V4 2/4] mm: vmscan: add more comments about cache_trim_mode Zhongkun He
2025-04-21 9:13 ` [PATCH V4 3/4] mm: add max swappiness arg to lru_gen for anonymous memory only Zhongkun He
2025-04-21 9:35 ` Muchun Song
2025-04-22 6:18 ` Zhongkun He [this message]
2025-05-07 7:10 ` [PATCH update] " Zhongkun He
2025-04-21 9:13 ` [PATCH V4 4/4] mm: using SWAPPINESS_ANON_ONLY in MGLRU Zhongkun He
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=CACSyD1MCfAAJ5R0y3Kn5u_a7RyhgZhiBwCF14uEKGAzs-7BbMQ@mail.gmail.com \
--to=hezhongkun.hzk@bytedance.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=muchun.song@linux.dev \
--cc=yosry.ahmed@linux.dev \
--cc=yuzhao@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