From: JP Kobryn <inwardvessel@gmail.com>
To: Chen Ridong <chenridong@huaweicloud.com>,
tj@kernel.org, hannes@cmpxchg.org, mkoutny@suse.com,
rostedt@goodmis.org, mhiramat@kernel.org,
mathieu.desnoyers@efficios.com, shakeel.butt@linux.dev
Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, lujialin4@huawei.com
Subject: Re: [PATCH -next] cgroup: increase maximum subsystem count from 16 to 32
Date: Thu, 29 Jan 2026 17:24:58 -0800 [thread overview]
Message-ID: <d1a0f008-1834-4e9d-8c6e-6ae7cffa4c08@gmail.com> (raw)
In-Reply-To: <20260129063133.209874-1-chenridong@huaweicloud.com>
Hi Chen,
On 1/28/26 10:31 PM, Chen Ridong wrote:
> From: Chen Ridong <chenridong@huawei.com>
>
> The current cgroup subsystem limit of 16 is insufficient, as the number of
> subsystems has already reached this maximum. Attempting to add new
> subsystems beyond this limit results in boot failures.
>
> This patch increases the maximum number of supported cgroup subsystems from
> 16 to 32, providing adequate headroom for future subsystem additions.
>
> Signed-off-by: Chen Ridong <chenridong@huawei.com>
> ---
[...]
I gave this a run with with 32 controllers enabled (16 pre-existing, 16
custom) and can confirm it works as expected.
Tested-by: JP Kobryn <inwardvessel@gmail.com>
Acked-by: JP Kobryn <inwardvessel@gmail.com>
prev parent reply other threads:[~2026-01-30 1:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 6:31 [PATCH -next] cgroup: increase maximum subsystem count from 16 to 32 Chen Ridong
2026-01-29 7:22 ` Chen Ridong
2026-01-29 9:23 ` Michal Koutný
2026-01-29 9:51 ` Chen Ridong
2026-01-29 18:33 ` Waiman Long
2026-01-30 0:41 ` Chen Ridong
2026-01-30 10:22 ` Michal Koutný
2026-01-31 3:00 ` Chen Ridong
2026-01-30 1:24 ` JP Kobryn [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=d1a0f008-1834-4e9d-8c6e-6ae7cffa4c08@gmail.com \
--to=inwardvessel@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=chenridong@huaweicloud.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=lujialin4@huawei.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mkoutny@suse.com \
--cc=rostedt@goodmis.org \
--cc=shakeel.butt@linux.dev \
--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