From: Shakeel Butt <shakeel.butt@linux.dev>
To: Baolin Wang <baolin.wang@linux.alibaba.com>
Cc: Kairui Song <ryncsn@gmail.com>,
akpm@linux-foundation.org, hannes@cmpxchg.org, david@kernel.org,
mhocko@kernel.org, zhengqi.arch@bytedance.com,
axelrasmussen@google.com, yuanchu@google.com,
weixugc@google.com, ljs@kernel.org, baohua@kernel.org,
kasong@tencent.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
Jingxiang Zeng <linuszeng@tencent.com>
Subject: Re: [PATCH] mm: vmscan: fix dirty folios throttling on cgroup v1 for MGLRU
Date: Wed, 1 Apr 2026 20:23:53 -0700 [thread overview]
Message-ID: <ac3gP_OWXGnejtwk@linux.dev> (raw)
In-Reply-To: <0498d924-d76a-4d82-8767-e6297442967a@linux.alibaba.com>
On Thu, Apr 02, 2026 at 10:51:37AM +0800, Baolin Wang wrote:
>
>
[...]
>
> > > This is v1 only and I don't care much but what is stopping you from moving away
> > > from v1?
> >
> > For example memsw?
> >
> > https://lore.kernel.org/linux-mm/q2x4drxpjbxcxgns6bjp446ynsxgl32ckcljqcol7posds4nit@3n3tjq35anvb/
> >
> > I remember Jingxiang's plan is to improve the page counter first.
>
> Additionally, we still have some existing users on cgroup v1, and they will
> need some time to migrate to cgroup v2.
Time is fine but is there any specific v1 feature which is a blocker for you.
The memsw is a known one and is the same for Google (data center). I am aiming
to provide memsw like behavior through my memcg_ext proposal but performance is
an open question. I am aiming to have a prototype before LSFMM to further the
discussion.
next prev parent reply other threads:[~2026-04-02 3:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 10:21 [PATCH] mm: vmscan: fix dirty folios throttling on cgroup v1 for MGLRU Baolin Wang
2026-03-27 15:30 ` Andrew Morton
2026-03-28 2:38 ` Baolin Wang
2026-03-27 16:41 ` Johannes Weiner
2026-03-27 17:59 ` Kairui Song
2026-04-01 20:32 ` Shakeel Butt
2026-04-02 2:44 ` Kairui Song
2026-04-02 2:51 ` Baolin Wang
2026-04-02 3:23 ` Shakeel Butt [this message]
2026-04-02 3:35 ` Baolin Wang
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=ac3gP_OWXGnejtwk@linux.dev \
--to=shakeel.butt@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=kasong@tencent.com \
--cc=linuszeng@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@kernel.org \
--cc=ryncsn@gmail.com \
--cc=weixugc@google.com \
--cc=yuanchu@google.com \
--cc=zhengqi.arch@bytedance.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.