[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aEIgtdrFbyNf4v85@archie.me>
Date: Fri, 6 Jun 2025 05:56:53 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Vishal Chourasia <vishalc@...ux.ibm.com>, Tejun Heo <tj@...nel.org>,
Johannes Weiner <hannes@...xchg.org>,
Michal KoutnĂ˝ <mkoutny@...e.com>,
Jonathan Corbet <corbet@....net>, cgroups@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
llong@...hat.com
Subject: Re: [PATCH v2] Documentation: cgroup: add section explaining
controller availability
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@...il.com>
--
An old man doll... just what I always wanted! - Clara
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists