[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZtIlC7pH17WkGXE6@slm.duckdns.org>
Date: Fri, 30 Aug 2024 10:01:15 -1000
From: Tejun Heo <tj@...nel.org>
To: Chen Ridong <chenridong@...wei.com>
Cc: lizefan.x@...edance.com, hannes@...xchg.org, longman@...hat.com,
adityakali@...gle.com, sergeh@...nel.org, mkoutny@...e.com,
cgroups@...r.kernel.org, linux-kernel@...r.kernel.org,
chenridong@...weicloud.com
Subject: Re: [PATCH v4 -next 00/12] cgroup:cpuset:separate legacy cgroup v1
code and put under config option
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
Powered by blists - more mailing lists