From: Chen Ridong <chenridong@huaweicloud.com>
To: "Michal Koutný" <mkoutny@suse.com>
Cc: tj@kernel.org, hannes@cmpxchg.org, rostedt@goodmis.org,
mhiramat@kernel.org, mathieu.desnoyers@efficios.com,
inwardvessel@gmail.com, shakeel.butt@linux.dev,
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: Sat, 31 Jan 2026 11:00:05 +0800 [thread overview]
Message-ID: <1f31d8d2-811d-4dff-b036-2eb201f623ba@huaweicloud.com> (raw)
In-Reply-To: <stsf73lnkx2luuak3a7oi3q4l5axosrxogi2lncw4dkndnc2ge@3tioqa6ww5q7>
On 2026/1/30 18:22, Michal Koutný wrote:
> On Thu, Jan 29, 2026 at 05:51:33PM +0800, Chen Ridong <chenridong@huaweicloud.com> wrote:
>> We compiled with 'make allmodconfig'.
>
> A-ha.
>
>> The BUILD_BUG_ON(CGROUP_SUBSYS_COUNT > 16) macro worked correctly.
>
> Good.
>
>> Can I propose increasing the maximum number now? If we switch certain configs to
>> default N and then a new subsystem is added later, the default configuration may
>> work fine, but it will become a problem under allmodconfig — which some users
>> actually rely on.
>>
>> Besides, this shouldn't be a major change, right?
>
> I'd like there to be gradual move away from legacy controllers code
> captured in config defaults.
> Could you adjust the commit message to stress out the allmodconfig tests?
>
Sure, will update.
--
Best regards,
Ridong
next prev parent reply other threads:[~2026-01-31 3:00 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 [this message]
2026-01-30 1:24 ` JP Kobryn
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=1f31d8d2-811d-4dff-b036-2eb201f623ba@huaweicloud.com \
--to=chenridong@huaweicloud.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=inwardvessel@gmail.com \
--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