[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7933e208-cd4f-2234-58cb-2e5b40e795d8@infradead.org>
Date: Tue, 21 Jun 2022 08:59:42 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Chengming Zhou <zhouchengming@...edance.com>, mingo@...hat.com,
peterz@...radead.org, juri.lelli@...hat.com,
vincent.guittot@...aro.org, dietmar.eggemann@....com,
rostedt@...dmis.org, bsegall@...gle.com, tj@...nel.org,
lizefan.x@...edance.com, hannes@...xchg.org, corbet@....net
Cc: cgroups@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sched: RT bandwidth interface for cgroup unified
hierarchy
Hi--
On 6/21/22 05:35, Chengming Zhou wrote:
> diff --git a/Documentation/admin-guide/cgroup-v2.rst b/Documentation/admin-guide/cgroup-v2.rst
> index 176298f2f4de..3d2949e16e04 100644
> --- a/Documentation/admin-guide/cgroup-v2.rst
> +++ b/Documentation/admin-guide/cgroup-v2.rst
> @@ -1055,6 +1055,19 @@ All time durations are in microseconds.
>
> The burst in the range [0, $MAX].
>
> + cpu.max.rt
> + A read-write two value file which exists on all cgroups when
two-value
> + CONFIG_RT_GROUP_SCHED enabled, to control CPU bandwidth for
is enabled,
> + RT threads in the task group.
> +
> + The maximum bandwidth limit. It's in the following format::
> +
> + $MAX $PERIOD
> +
> + which indicates that RT threads in the group may consume upto
up to
> + $MAX in each $PERIOD duration. "max" for $MAX indicates no
> + limit. If only one number is written, $MAX is updated.
--
~Randy
Powered by blists - more mailing lists