From: Chen Ridong <chenridong@huaweicloud.com>
To: hannes@cmpxchg.org, mhocko@kernel.org, roman.gushchin@linux.dev,
shakeel.butt@linux.dev, muchun.song@linux.dev,
akpm@linux-foundation.org, axelrasmussen@google.com,
yuanchu@google.com, weixugc@google.com, david@kernel.org,
zhengqi.arch@bytedance.com, lorenzo.stoakes@oracle.com
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, lujialin4@huawei.com,
chenridong@huaweicloud.com
Subject: [PATCH -next v2 0/2] memcg cleanups
Date: Wed, 10 Dec 2025 07:11:40 +0000 [thread overview]
Message-ID: <20251210071142.2043478-1-chenridong@huaweicloud.com> (raw)
From: Chen Ridong <chenridong@huawei.com>
This series cleans up two helpers in memcg:
1/2 moves mem_cgroup_usage() to memcontrol-v1.c
2/2 removes mem_cgroup_size()
Both are code moves/removals with no behavior change.
---
Change from v1:
1. Added CONFIG_MEMCG compilation guard to apply_proportional_protection()
Chen Ridong (2):
memcg: move mem_cgroup_usage memcontrol-v1.c
memcg: remove mem_cgroup_size()
include/linux/memcontrol.h | 7 -------
mm/memcontrol-v1.c | 22 ++++++++++++++++++++++
mm/memcontrol-v1.h | 2 --
mm/memcontrol.c | 27 ---------------------------
mm/vmscan.c | 8 +++++---
5 files changed, 27 insertions(+), 39 deletions(-)
--
2.34.1
next reply other threads:[~2025-12-10 7:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-10 7:11 Chen Ridong [this message]
2025-12-10 7:11 ` [PATCH -next v2 1/2] memcg: move mem_cgroup_usage memcontrol-v1.c Chen Ridong
2025-12-10 8:01 ` Michal Hocko
2025-12-10 16:28 ` Johannes Weiner
2025-12-10 7:11 ` [PATCH -next v2 2/2] memcg: remove mem_cgroup_size() Chen Ridong
2025-12-10 8:05 ` Michal Hocko
2025-12-10 8:31 ` Chen Ridong
2025-12-10 8:37 ` Michal Hocko
2025-12-10 8:42 ` Chen Ridong
2025-12-10 16:36 ` Johannes Weiner
2025-12-11 0:43 ` Chen Ridong
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=20251210071142.2043478-1-chenridong@huaweicloud.com \
--to=chenridong@huaweicloud.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=cgroups@vger.kernel.org \
--cc=david@kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=lujialin4@huawei.com \
--cc=mhocko@kernel.org \
--cc=muchun.song@linux.dev \
--cc=roman.gushchin@linux.dev \
--cc=shakeel.butt@linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).