From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Mike Galbraith <efault@gmx.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: RFC [patch] sched,cgroup_sched: convince RT_GROUP_SCHED throttle to work
Date: Sat, 14 Apr 2012 13:10:47 +0200 [thread overview]
Message-ID: <1334401847.2528.65.camel@twins> (raw)
In-Reply-To: <1334048925.7524.21.camel@marge.simpson.net>
On Tue, 2012-04-10 at 11:08 +0200, Mike Galbraith wrote:
> sched,rt: fix isolated CPUs leaving root_task_group indefinitely throttled
>
> Root task group bandwidth replenishment must service all CPUs regardless of
> where it was last started.
>
> Signed-off-by: Mike Galbraith <efault@gmx.de>
> ---
> kernel/sched/rt.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> --- a/kernel/sched/rt.c
> +++ b/kernel/sched/rt.c
> @@ -782,6 +782,19 @@ static int do_sched_rt_period_timer(stru
> const struct cpumask *span;
>
> span = sched_rt_period_mask();
> +#ifdef CONFIG_RT_GROUP_SCHED
> + /*
> + * FIXME: isolated CPUs should really leave the root task group,
No no, that's the wrong fix, the right fix is to remove isolcpus :-)
> + * whether they are isolcpus or were isolated via cpusets, lest
> + * the timer run on a CPU which does not service all runqueues,
> + * potentially leaving other CPUs indefinitely throttled. If
> + * isolation is really required, the user will turn the throttle
> + * off to kill the perturbations it causes anyway. Meanwhile,
> + * this maintains functionality for boot and/or troubleshooting.
> + */
> + if (rt_b == &root_task_group.rt_bandwidth)
> + span = cpu_online_mask;
> +#endif
> for_each_cpu(i, span) {
> int enqueue = 0;
> struct rt_rq *rt_rq = sched_rt_period_rt_rq(rt_b, i);
I guess the alternative 'fix' is to not account the rt_runtime on
isolated cpus.. does something like the below actually work?
---
kernel/sched/rt.c | 3 +++
1 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/kernel/sched/rt.c b/kernel/sched/rt.c
index 44af55e..dc2b5b6 100644
--- a/kernel/sched/rt.c
+++ b/kernel/sched/rt.c
@@ -922,6 +922,9 @@ static void update_curr_rt(struct rq *rq)
if (!rt_bandwidth_enabled())
return;
+ if (cpumask_test_cpu(cpu_of(rq), cpu_isolated_map))
+ return;
+
for_each_sched_rt_entity(rt_se) {
rt_rq = rt_rq_of_se(rt_se);
next prev parent reply other threads:[~2012-04-14 11:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 9:08 [patch] sched,rt: non-isolated cores lift isolcpus throttle for CONFIG_RT_GROUP_SCHED Mike Galbraith
2012-04-03 9:19 ` [patch] sched,rt: let the user see rt queues in /proc/sched_debug Mike Galbraith
2012-04-07 8:58 ` [patch] sched,cgroup_sched: fix up task_groups list buglet Mike Galbraith
2012-04-07 9:54 ` RFC [patch] sched,cgroup_sched: convince RT_GROUP_SCHED throttle to work Mike Galbraith
2012-04-10 9:08 ` Mike Galbraith
2012-04-14 11:10 ` Peter Zijlstra [this message]
2012-04-15 3:37 ` Mike Galbraith
2012-04-15 3:44 ` Mike Galbraith
2012-04-15 4:51 ` Mike Galbraith
2012-04-18 5:20 ` Yong Zhang
2012-04-18 6:27 ` Mike Galbraith
2012-04-18 7:48 ` Yong Zhang
2012-04-18 8:38 ` Mike Galbraith
2012-04-19 6:34 ` Yong Zhang
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=1334401847.2528.65.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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