From: Bagas Sanjaya <bagasdotme@gmail.com>
To: "Vishal Chourasia" <vishalc@linux.ibm.com>,
"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, llong@redhat.com
Subject: Re: [PATCH v2] Documentation: cgroup: add section explaining controller availability
Date: Fri, 6 Jun 2025 05:56:53 +0700 [thread overview]
Message-ID: <aEIgtdrFbyNf4v85@archie.me> (raw)
In-Reply-To: <20250605145421.193189-2-vishalc@linux.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 932 bytes --]
On Thu, Jun 05, 2025 at 08:24:22PM +0530, Vishal Chourasia wrote:
> A new documentation section titled "Availability" has been added to
> describe the meaning of a controller being available in a cgroup,
> complementing the existing "Enabling and Disabling" section.
'Add "Availability" section to Control Group v2 docs. It describes ...'
> +Availablity
> +~~~~~~~~~~~
> +
> +A controller is available in a cgroup when it is supported by the kernel (i.e.,
> +compiled in, not disabled and not attached to a v1 hierarchy) and listed in the
> +"cgroup.controllers" file. Availability means the controller's interface files
> +are exposed in the cgroup’s directory, allowing the distribution of the target
> +resource to be observed or controlled within that cgroup.
> +
The wording LGTM, thanks!
Reviewed-by: Bagas Sanjaya <bagasdotme@gmail.com>
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-06-05 22:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-05 14:54 [PATCH v2] Documentation: cgroup: add section explaining controller availability Vishal Chourasia
2025-06-05 15:50 ` Michal Koutný
2025-06-05 22:56 ` Bagas Sanjaya [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=aEIgtdrFbyNf4v85@archie.me \
--to=bagasdotme@gmail.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 \
--cc=vishalc@linux.ibm.com \
/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).