49 lines
1.5 KiB
Diff
49 lines
1.5 KiB
Diff
From: Peter Zijlstra <peterz@infradead.org>
|
|
Date: Tue, 18 Oct 2011 22:03:48 +0200
|
|
Subject: sched: Do not throttle due to PI boosting
|
|
|
|
When a runqueue has rt_runtime_us = 0 then the only way it can
|
|
accumulate rt_time is via PI boosting. Though that causes the runqueue
|
|
to be throttled and replenishing does not change anything due to
|
|
rt_runtime_us = 0. So avoid that situation by clearing rt_time and
|
|
skip the throttling alltogether.
|
|
|
|
[ tglx: Preliminary changelog ]
|
|
|
|
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
|
|
---
|
|
kernel/sched_rt.c | 20 ++++++++++++++++++--
|
|
1 file changed, 18 insertions(+), 2 deletions(-)
|
|
|
|
Index: linux-3.2/kernel/sched_rt.c
|
|
===================================================================
|
|
--- linux-3.2.orig/kernel/sched_rt.c
|
|
+++ linux-3.2/kernel/sched_rt.c
|
|
@@ -659,8 +659,24 @@ static int sched_rt_runtime_exceeded(str
|
|
return 0;
|
|
|
|
if (rt_rq->rt_time > runtime) {
|
|
- rt_rq->rt_throttled = 1;
|
|
- printk_once(KERN_WARNING "sched: RT throttling activated\n");
|
|
+ struct rt_bandwidth *rt_b = sched_rt_bandwidth(rt_rq);
|
|
+
|
|
+ /*
|
|
+ * Don't actually throttle groups that have no runtime assigned
|
|
+ * but accrue some time due to boosting.
|
|
+ */
|
|
+ if (likely(rt_b->rt_runtime)) {
|
|
+ rt_rq->rt_throttled = 1;
|
|
+ printk_once(KERN_WARNING "sched: RT throttling activated\n");
|
|
+ } else {
|
|
+ /*
|
|
+ * In case we did anyway, make it go away,
|
|
+ * replenishment is a joke, since it will replenish us
|
|
+ * with exactly 0 ns.
|
|
+ */
|
|
+ rt_rq->rt_time = 0;
|
|
+ }
|
|
+
|
|
if (rt_rq_throttled(rt_rq)) {
|
|
sched_rt_rq_dequeue(rt_rq);
|
|
return 1;
|