From: Tejun Heo <tj@kernel.org>
To: Chen Ridong <chenridong@huawei.com>
Cc: lizefan.x@bytedance.com, hannes@cmpxchg.org, longman@redhat.com,
adityakali@google.com, sergeh@kernel.org, mkoutny@suse.com,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
chenridong@huaweicloud.com
Subject: Re: [PATCH v4 -next 00/12] cgroup:cpuset:separate legacy cgroup v1 code and put under config option
Date: Fri, 30 Aug 2024 10:01:15 -1000 [thread overview]
Message-ID: <ZtIlC7pH17WkGXE6@slm.duckdns.org> (raw)
In-Reply-To: <20240830100229.953012-1-chenridong@huawei.com>
On Fri, Aug 30, 2024 at 10:02:17AM +0000, Chen Ridong wrote:
> Cgroups v2 have been around for a while and many users have fully adopted
> them, so they never use cgroups v1 features and functionality. Yet they
> have to "pay" for the cgroup v1 support anyway:
> 1) the kernel binary contains an unused cgroup v1 code,
> 2) some code paths have additional checks which are not needed,
> 3) some common structures like task_struct and mem_cgroup contain unused
> cgroup v1-specific members.
>
> Cgroup memory controller has already separated legacy code to
> memory-v1.c. So it is time to do the same thing for cpuset controller.
>
> This patchset aims to do:
> 1) moving cgroup v1-specific cpuset code to the new cpuset-v1.c file,
> 2) putting definitions shared by cpuset.c and cpuset-v1.c into the
> cpuset-internal.h header,
> 3) introducing the CONFIG_CPUSETS_V1 config option, turned off by default,
> 4) making cpuset-v1.c to compile only if CONFIG_CPUSETS_V1 is set.
Applied the series to cgroup/for-6.12.
Thanks.
--
tejun
prev parent reply other threads:[~2024-08-30 20:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 10:02 Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 01/12] cgroup/cpuset: introduce cpuset-v1.c Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 02/12] cgroup/cpuset: move common code to cpuset-internal.h Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 03/12] cgroup/cpuset: move memory_pressure to cpuset-v1.c Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 04/12] cgroup/cpuset: move relax_domain_level " Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 05/12] cgroup/cpuset: move memory_spread " Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 06/12] cgroup/cpuset: add callback_lock helper Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 07/12] cgroup/cpuset: move legacy hotplug update to cpuset-v1.c Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 08/12] cgroup/cpuset: move validate_change_legacy " Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 09/12] cgroup/cpuset: move v1 interfaces " Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 10/12] cgroup/cpuset: rename functions shared between v1 and v2 Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 11/12] cgroup/cpuset: guard cpuset-v1 code under CONFIG_CPUSETS_V1 Chen Ridong
2024-08-30 10:02 ` [PATCH v4 -next 12/12] cgroup/cpuset: add sefltest for cpuset v1 Chen Ridong
2024-08-30 14:33 ` [PATCH v4 -next 00/12] cgroup:cpuset:separate legacy cgroup v1 code and put under config option Waiman Long
2024-08-30 20:01 ` Tejun Heo [this message]
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=ZtIlC7pH17WkGXE6@slm.duckdns.org \
--to=tj@kernel.org \
--cc=adityakali@google.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=sergeh@kernel.org \
/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
all inboxes | Powered by JetHome®