From: Waiman Long <longman@redhat.com>
To: Chen Ridong <chenridong@huawei.com>,
tj@kernel.org, lizefan.x@bytedance.com, hannes@cmpxchg.org,
mkoutny@suse.com
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 -next 00/11] cgroup:cpuset:separate legacy cgroup v1 code and put under config option
Date: Sun, 25 Aug 2024 13:20:06 -0400 [thread overview]
Message-ID: <6dde95a0-2cad-4ca8-9ea3-2b4c6e70db93@redhat.com> (raw)
In-Reply-To: <20240823100110.472120-1-chenridong@huawei.com>
On 8/23/24 06:00, 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.
>
> This patchset is based on -next commit c79c85875f1a ("Add linux-next
> specific files for 20240823") and assumes that "Some optimizations about
> cpuset" series are merged, which are applied to cgroup/for-6.12.
>
>
> Chen Ridong (11):
> cgroup/cpuset: introduce cpuset-v1.c
> cgroup/cpuset: move common code to cpuset-internal.h
> cgroup/cpuset: move memory_pressure to cpuset-v1.c
> cgroup/cpuset: move relax_domain_level to cpuset-v1.c
> cgroup/cpuset: move memory_spread to cpuset-v1.c
> cgroup/cpuset: add callback_lock helper
> cgroup/cpuset: move legacy hotplug update to cpuset-v1.c
> cgroup/cpuset: move validate_change_legacy to cpuset-v1.c
> cgroup/cpuset: move v1 interfaces to cpuset-v1.c
> cgroup/cpuset: guard cpuset-v1 code under CONFIG_CPUSETS_V1
> cgroup/cpuset: add sefltest for cpuset v1
>
> MAINTAINERS | 3 +
> include/linux/cpuset.h | 8 +-
> init/Kconfig | 13 +
> kernel/cgroup/Makefile | 1 +
> kernel/cgroup/cpuset-internal.h | 307 +++++++
> kernel/cgroup/cpuset-v1.c | 565 ++++++++++++
> kernel/cgroup/cpuset.c | 850 +-----------------
> .../selftests/cgroup/test_cpuset_v1_base.sh | 77 ++
> 8 files changed, 987 insertions(+), 837 deletions(-)
> create mode 100644 kernel/cgroup/cpuset-internal.h
> create mode 100644 kernel/cgroup/cpuset-v1.c
> create mode 100755 tools/testing/selftests/cgroup/test_cpuset_v1_base.sh
>
Patch 2 doesn't apply to the latest cgroup/for-6.12 branch of the cgroup
tree. You will have to update the patch series.
Cheers,
Longman
next prev parent reply other threads:[~2024-08-25 17:20 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 10:00 Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 01/11] cgroup/cpuset: introduce cpuset-v1.c Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 02/11] cgroup/cpuset: move common code to cpuset-internal.h Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 03/11] cgroup/cpuset: move memory_pressure to cpuset-v1.c Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 04/11] cgroup/cpuset: move relax_domain_level " Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 05/11] cgroup/cpuset: move memory_spread " Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 06/11] cgroup/cpuset: add callback_lock helper Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 07/11] cgroup/cpuset: move legacy hotplug update to cpuset-v1.c Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 08/11] cgroup/cpuset: move validate_change_legacy " Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 09/11] cgroup/cpuset: move v1 interfaces " Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 10/11] cgroup/cpuset: guard cpuset-v1 code under CONFIG_CPUSETS_V1 Chen Ridong
2024-08-25 17:25 ` Waiman Long
2024-08-26 1:34 ` Chen Ridong
2024-08-26 2:18 ` Waiman Long
2024-08-26 12:53 ` Chen Ridong
2024-08-23 10:01 ` [PATCH v1 -next 11/11] cgroup/cpuset: add sefltest for cpuset v1 Chen Ridong
2024-08-25 17:20 ` Waiman Long [this message]
2024-08-26 1:36 ` [PATCH v1 -next 00/11] cgroup:cpuset:separate legacy cgroup v1 code and put under config option chenridong
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=6dde95a0-2cad-4ca8-9ea3-2b4c6e70db93@redhat.com \
--to=longman@redhat.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huawei.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mkoutny@suse.com \
--cc=tj@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®