From: Michal Hocko <mhocko@suse.com>
To: xu xin <xu.xin.sc@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Matthew Wilcox <willy@infradead.org>,
xu.xin16@zte.com.cn, david@redhat.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, wang.yaxin@zte.com.cn,
yang.yang29@zte.com.cn
Subject: Re: [PATCH RESEND 1/6] memcontrol: rename mem_cgroup_scan_tasks()
Date: Fri, 25 Apr 2025 16:30:21 +0200 [thread overview]
Message-ID: <aAucfUFeqHBaHfKs@tiehlicka> (raw)
In-Reply-To: <aAjbb1fBR-tq1h93@casper.infradead.org>
On Wed 23-04-25 13:22:07, Matthew Wilcox wrote:
> On Tue, Apr 22, 2025 at 04:29:52PM -0700, Andrew Morton wrote:
> > Patchset looks nice to me, thanks. I'll await reviewer feedback before
> > proceeding.
>
> I thought we had a policy against adding new features to memcg-v1?
> Certainly adding the feature to memcg-v2 would be a requirement before
> it could be added to v1.
Completely agreed! Is there any reason why v2 was not the first choice?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2025-04-25 14:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 11:14 [PATCH RESEND 0/6] support ksm_stat showing at cgroup level xu.xin16
2025-04-22 11:19 ` [PATCH RESEND 1/6] memcontrol: rename mem_cgroup_scan_tasks() xu xin
2025-04-22 23:29 ` Andrew Morton
2025-04-23 12:22 ` Matthew Wilcox
2025-04-25 14:30 ` Michal Hocko [this message]
2025-04-22 11:20 ` [PATCH RESEND 2/6] memcontrol: introduce the new mem_cgroup_scan_tasks() xu xin
2025-04-22 11:21 ` [PATCH RESEND 3/6] memcontrol-v1: introduce ksm_stat at cgroup level xu xin
2025-04-22 11:21 ` [PATCH RESEND 4/6] memcontrol-v1: add ksm_zero_pages in cgroup/memory.ksm_stat xu xin
2025-04-22 11:22 ` [PATCH RESEND 5/6] memcontrol-v1: add ksm_merging_pages " xu xin
2025-04-22 11:22 ` [PATCH RESEND 6/6] memcontrol-v1: add ksm_profit " xu xin
2025-04-23 8:21 ` kernel test robot
2025-04-23 13:08 ` [PATCH RESEND 0/6] support ksm_stat showing at cgroup level David Hildenbrand
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=aAucfUFeqHBaHfKs@tiehlicka \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=wang.yaxin@zte.com.cn \
--cc=willy@infradead.org \
--cc=xu.xin.sc@gmail.com \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/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.