From: Randy Dunlap <rdunlap@infradead.org>
To: Chengming Zhou <zhouchengming@bytedance.com>,
mingo@redhat.com, peterz@infradead.org, juri.lelli@redhat.com,
vincent.guittot@linaro.org, dietmar.eggemann@arm.com,
rostedt@goodmis.org, bsegall@google.com, tj@kernel.org,
lizefan.x@bytedance.com, hannes@cmpxchg.org, corbet@lwn.net
Cc: cgroups@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched: RT bandwidth interface for cgroup unified hierarchy
Date: Tue, 21 Jun 2022 08:59:42 -0700 [thread overview]
Message-ID: <7933e208-cd4f-2234-58cb-2e5b40e795d8@infradead.org> (raw)
In-Reply-To: <20220621123542.1444-1-zhouchengming@bytedance.com>
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
next prev parent reply other threads:[~2022-06-21 16:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 12:35 Chengming Zhou
2022-06-21 15:59 ` Randy Dunlap [this message]
2022-06-22 1:52 ` [External] " Chengming Zhou
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=7933e208-cd4f-2234-58cb-2e5b40e795d8@infradead.org \
--to=rdunlap@infradead.org \
--cc=bsegall@google.com \
--cc=cgroups@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=dietmar.eggemann@arm.com \
--cc=hannes@cmpxchg.org \
--cc=juri.lelli@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan.x@bytedance.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=zhouchengming@bytedance.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
all inboxes | Powered by JetHome®