mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Waiman Long <llong@redhat.com>
To: shashank.mahadasyam@sony.com, "Tejun Heo" <tj@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Jonathan Corbet" <corbet@lwn.net>
Cc: cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Shinya Takumi <shinya.takumi@sony.com>
Subject: Re: [PATCH 2/2] cgroup, docs: Document interaction of RT processes with cpu controller
Date: Wed, 5 Mar 2025 09:16:15 -0500	[thread overview]
Message-ID: <d259ba35-a4a5-4e01-b539-85f2080fdd33@redhat.com> (raw)
In-Reply-To: <20250305-rt-and-cpu-controller-doc-v1-2-7b6a6f5ff43d@sony.com>


On 3/4/25 11:12 PM, Shashank Balaji via B4 Relay wrote:
> From: Shashank Balaji <shashank.mahadasyam@sony.com>
>
> If the cpu controller is enabled in a CONFIG_RT_GROUP_SCHED
> disabled setting, cpu.stat and cpu.pressure account for realtime
> processes, and cpu.uclamp.{min, max} affect realtime processes as well.
> None of the other interface files are affected by or affect realtime
> processes.
>
> Signed-off-by: Shashank Balaji <shashank.mahadasyam@sony.com>
> ---
>   Documentation/admin-guide/cgroup-v2.rst | 18 +++++++++++++-----
>   1 file changed, 13 insertions(+), 5 deletions(-)
>
> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> index f293a13b42ed69e7c6bf5e974cb86e228411af4e..2c267f42e5fef9c4e2c3530ce73330d680b9b2dc 100644
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -1095,7 +1095,9 @@ realtime processes irrespective of CONFIG_RT_GROUP_SCHED.
>   CPU Interface Files
>   ~~~~~~~~~~~~~~~~~~~
>   
> -All time durations are in microseconds.
> +All time durations are in microseconds. Only cpu.stat and cpu.pressure account
> +for realtime processes, and only cpu.uclamp.min and cpu.uclamp.max
> +affect realtime processes.
>   
>     cpu.stat
>   	A read-only flat-keyed file.
> @@ -1115,6 +1117,9 @@ All time durations are in microseconds.
>   	- nr_bursts
>   	- burst_usec
>   
> +    The runtime of realtime processes is accounted for only by the usage_usec,
> +	user_usec, and system_usec fields.
> +

Alignment problem!

Anyway, I am not familiar enough with these cpu control files to give a 
review yet.

Cheers,
Longman

>     cpu.weight
>   	A read-write single value file which exists on non-root
>   	cgroups.  The default is "100".
> @@ -1158,8 +1163,9 @@ All time durations are in microseconds.
>     cpu.pressure
>   	A read-write nested-keyed file.
>   
> -	Shows pressure stall information for CPU. See
> -	:ref:`Documentation/accounting/psi.rst <psi>` for details.
> +	Shows pressure stall information for CPU, including the contribution of
> +	realtime processes. See :ref:`Documentation/accounting/psi.rst <psi>`
> +	for details.
>   
>     cpu.uclamp.min
>           A read-write single value file which exists on non-root cgroups.
> @@ -1170,7 +1176,8 @@ All time durations are in microseconds.
>   
>           This interface allows reading and setting minimum utilization clamp
>           values similar to the sched_setattr(2). This minimum utilization
> -        value is used to clamp the task specific minimum utilization clamp.
> +        value is used to clamp the task specific minimum utilization clamp,
> +        including those of realtime processes.
>   
>           The requested minimum utilization (protection) is always capped by
>           the current value for the maximum utilization (limit), i.e.
> @@ -1185,7 +1192,8 @@ All time durations are in microseconds.
>   
>           This interface allows reading and setting maximum utilization clamp
>           values similar to the sched_setattr(2). This maximum utilization
> -        value is used to clamp the task specific maximum utilization clamp.
> +        value is used to clamp the task specific maximum utilization clamp,
> +        including those of realtime processes.
>   
>     cpu.idle
>   	A read-write single value file which exists on non-root cgroups.
>


  reply	other threads:[~2025-03-05 14:16 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-05  4:12 [PATCH 0/2] cgroup, docs: Clarify interaction of RT processes with cgroup v2 " Shashank Balaji via B4 Relay
2025-03-05  4:12 ` [PATCH 1/2] cgroup, docs: Be explicit about independence of RT_GROUP_SCHED and non-cpu controllers Shashank Balaji via B4 Relay
2025-03-05 14:13   ` Waiman Long
2025-03-05 16:15   ` Michal Koutný
2025-03-05 18:44   ` Tejun Heo
2025-03-05  4:12 ` [PATCH 2/2] cgroup, docs: Document interaction of RT processes with cpu controller Shashank Balaji via B4 Relay
2025-03-05 14:16   ` Waiman Long [this message]
2025-03-06 10:23     ` Shashank.Mahadasyam
2025-03-05 16:19   ` Michal Koutný
2025-03-06 11:02     ` Shashank.Mahadasyam
2025-03-10 17:14       ` Michal Koutný
2025-03-28 10:45         ` Shashank.Mahadasyam
2025-04-02 12:49           ` Michal Koutný

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=d259ba35-a4a5-4e01-b539-85f2080fdd33@redhat.com \
    --to=llong@redhat.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=mkoutny@suse.com \
    --cc=shashank.mahadasyam@sony.com \
    --cc=shinya.takumi@sony.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

all inboxes | Powered by JetHome®