[PATCH 2/5] sched: pull only one task during NEWIDLE balancing to limit critical section

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Gregory Haskins
Date: Monday, August 25, 2008 - 1:15 pm

git-id c4acb2c0669c5c5c9b28e9d02a34b5c67edf7092 attempted to limit
newidle critical section length by stopping after at least one task
was moved.  Further investigation has shown that there are other
paths nested further inside the algorithm which still remain that allow
long latencies to occur with newidle balancing.  This patch applies
the same technique inside balance_tasks() to limit the duration of
this optional balancing operation.

Signed-off-by: Gregory Haskins <ghaskins@novell.com>
CC: Nick Piggin <npiggin@suse.de>
---

 kernel/sched.c |    6 ++++--
 1 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/kernel/sched.c b/kernel/sched.c
index 6a43c89..6e0bde6 100644
--- a/kernel/sched.c
+++ b/kernel/sched.c
@@ -2963,9 +2963,11 @@ next:
 	rem_load_move -= p->se.load.weight;
 
 	/*
-	 * We only want to steal up to the prescribed amount of weighted load.
+	 * We only want to steal up to the prescribed amount of weighted load
+	 * and we don't want to take more than one task if we are NEWLY idle
+	 * since this can cause unbounded latencies
 	 */
-	if (rem_load_move > 0) {
+	if (idle != CPU_NEWLY_IDLE && rem_load_move > 0) {
 		if (p->prio < *this_best_prio)
 			*this_best_prio = p->prio;
 		p = iterator->next(iterator->arg);

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH 0/5] sched: misc rt fixes for tip/sched/devel, Gregory Haskins, (Mon Aug 25, 1:15 pm)
[PATCH 2/5] sched: pull only one task during NEWIDLE balan ..., Gregory Haskins, (Mon Aug 25, 1:15 pm)
[PATCH 3/5] sched: make double-lock-balance fair, Gregory Haskins, (Mon Aug 25, 1:15 pm)
Re: [PATCH 3/5] sched: make double-lock-balance fair, Nick Piggin, (Mon Aug 25, 11:14 pm)
Re: [PATCH 3/5] sched: make double-lock-balance fair, Gregory Haskins, (Tue Aug 26, 5:23 am)
[PATCH v2 0/6] Series short description, Gregory Haskins, (Tue Aug 26, 10:34 am)
[PATCH v2 3/6] sched: make double-lock-balance fair, Gregory Haskins, (Tue Aug 26, 10:35 am)
Re: [PATCH 3/5] sched: make double-lock-balance fair, Nick Piggin, (Tue Aug 26, 11:36 pm)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Peter Zijlstra, (Wed Aug 27, 1:21 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Peter Zijlstra, (Wed Aug 27, 1:25 am)
Re: [PATCH v2 0/6] Series short description, Peter Zijlstra, (Wed Aug 27, 1:33 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Peter Zijlstra, (Wed Aug 27, 3:41 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Peter Zijlstra, (Wed Aug 27, 4:07 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Russell King, (Wed Aug 27, 4:17 am)
Re: [PATCH 3/5] sched: make double-lock-balance fair, Gregory Haskins, (Wed Aug 27, 4:41 am)
Re: [PATCH 3/5] sched: make double-lock-balance fair, Nick Piggin, (Wed Aug 27, 4:53 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Gregory Haskins, (Wed Aug 27, 5:00 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Gregory Haskins, (Wed Aug 27, 5:02 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Gregory Haskins, (Wed Aug 27, 5:03 am)
Re: [PATCH 3/5] sched: make double-lock-balance fair, Gregory Haskins, (Wed Aug 27, 5:10 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Gregory Haskins, (Wed Aug 27, 5:13 am)
Re: [PATCH v2 3/6] sched: make double-lock-balance fair, Ralf Baechle, (Fri Aug 29, 5:49 am)
[TIP/SCHED/DEVEL PATCH v3 0/6] sched: misc rt fixes, Gregory Haskins, (Thu Sep 4, 5:54 am)