From: Vishal Chourasia <vishalc@linux.ibm.com>
To: Waiman Long <llong@redhat.com>
Cc: "Tejun Heo" <tj@kernel.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Michal Koutný" <mkoutny@suse.com>,
"Jonathan Corbet" <corbet@lwn.net>,
cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Documentation: cgroup: clarify controller enabling semantics
Date: Wed, 28 May 2025 23:07:29 +0530 [thread overview]
Message-ID: <aDdJ2apexd2sJmm3@linux.ibm.com> (raw)
In-Reply-To: <a9d0e503-ec70-41a7-adb2-989082e4d9f2@redhat.com>
Hi Longman,
On Wed, May 28, 2025 at 11:45:29AM -0400, Waiman Long wrote:
>
> On 5/28/25 11:23 AM, Waiman Long wrote:
> > I believe breaking the sentence into two separate components
> > is actually making it less correct. There are implicit
> > controllers that are always enabled and do not show up in
> > cgroup.controllers. Prime examples are perf_event and
> > freezer. IOW, only controllers that are available and need
> > to be explicitly enabled will show up.
>
> A correction: The cgroup.controllers file shows the controllers
> that are available in the current cgroup and which have to be
> explicitly enabled in cgroup.subtree_control to make them
> available in the child cgroups.
Thank you for pointing it out.
Vishal
>
> Cheers,
> Longman
>
prev parent reply other threads:[~2025-05-28 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 8:53 [PATCH] Documentation: cgroup: clarify controller enabling semantics Vishal Chourasia
2025-05-27 9:58 ` Michal Koutný
2025-05-28 13:18 ` Vishal Chourasia
2025-05-28 17:05 ` Michal Koutný
2025-05-28 18:08 ` Vishal Chourasia
2025-05-28 13:31 ` Vishal Chourasia
2025-05-27 10:04 ` Bagas Sanjaya
2025-05-28 17:28 ` Vishal Chourasia
2025-05-28 15:23 ` Waiman Long
2025-05-28 15:45 ` Waiman Long
2025-05-28 17:37 ` Vishal Chourasia [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=aDdJ2apexd2sJmm3@linux.ibm.com \
--to=vishalc@linux.ibm.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=hannes@cmpxchg.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llong@redhat.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;
as well as URLs for NNTP newsgroup(s).