From: "Michal Koutný" <mkoutny@suse.com>
To: Chengming Zhou <zhouchengming@bytedance.com>
Cc: rdunlap@infradead.org, 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, cgroups@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [External] Re: [PATCH v2] sched: RT bandwidth interface for cgroup unified hierarchy
Date: Thu, 23 Jun 2022 09:51:02 +0200 [thread overview]
Message-ID: <20220623075102.GJ27251@blackbody.suse.cz> (raw)
In-Reply-To: <888b6885-5380-e21f-260f-eb1bb89679c3@bytedance.com>
On Thu, Jun 23, 2022 at 10:23:26AM +0800, Chengming Zhou <zhouchengming@bytedance.com> wrote:
> I don't know why v2 differ from v1 in the RT bandwidth control.. Is there
> some links of explanation? (CFS bandwidth control can work on v2 now.)
You can see some ideas in [1] (the v1 API allows configurations that are
not implemented).
And I'd also say more generally, that applying throttling to an RT task
is already a lost game (either it's a runaway meaning there's a bug
elsewhere or the RT task won't have sufficient runtime which defeats its
RTness).
> If the problem can't be solved, we have to unset CONFIG_RT_GROUP_SCHED.
AFAICT, this was enough so far (but RT group scheduling can still be
(re)worked).
HTH,
Michal
[1] https://www.kernel.org/doc/html/latest/scheduler/sched-rt-group.html
prev parent reply other threads:[~2022-06-23 7:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-22 1:55 Chengming Zhou
2022-06-22 2:06 ` Randy Dunlap
2022-06-22 17:39 ` Michal Koutný
2022-06-23 2:23 ` [External] " Chengming Zhou
2022-06-23 7:51 ` Michal Koutný [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=20220623075102.GJ27251@blackbody.suse.cz \
--to=mkoutny@suse.com \
--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=rdunlap@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®