From: Peter Williams <pwil3058@bigpond.net.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Con Kolivas <kernel@kolivas.org>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
Ingo Molnar <mingo@elte.hu>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Mike Galbraith <efault@gmx.de>,
"Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH] sched: improve stability of smpnice load balancing
Date: Thu, 30 Mar 2006 09:29:25 +1100 [thread overview]
Message-ID: <442B0A45.90808@bigpond.net.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
Problem:
Due to an injudicious piece of code near the end of find_busiest_group()
smpnice load balancing is too aggressive resulting in excessive movement
of tasks from one CPU to another.
Solution:
Remove the offending code. The thinking that caused it to be included
became invalid when find_busiest_queue() was modified to use average
load per task (on the relevant run queue) instead of SCHED_LOAD_SCALE
when evaluating small imbalance values to see whether they warranted
being moved.
Signed-off-by: Peter Williams <pwil3058@bigpond.com.au>
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
[-- Attachment #2: smpnice-increase-stability --]
[-- Type: text/plain, Size: 704 bytes --]
Index: MM-2.6.X/kernel/sched.c
===================================================================
--- MM-2.6.X.orig/kernel/sched.c 2006-03-29 16:18:37.000000000 +1100
+++ MM-2.6.X/kernel/sched.c 2006-03-29 16:20:37.000000000 +1100
@@ -2290,13 +2290,10 @@ find_busiest_group(struct sched_domain *
pwr_move /= SCHED_LOAD_SCALE;
/* Move if we gain throughput */
- if (pwr_move > pwr_now)
- *imbalance = busiest_load_per_task;
- /* or if there's a reasonable chance that *imbalance is big
- * enough to cause a move
- */
- else if (*imbalance <= busiest_load_per_task / 2)
+ if (pwr_move <= pwr_now)
goto out_balanced;
+
+ *imbalance = busiest_load_per_task;
}
return busiest;
reply other threads:[~2006-03-29 22:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=442B0A45.90808@bigpond.net.au \
--to=pwil3058@bigpond.net.au \
--cc=akpm@osdl.org \
--cc=efault@gmx.de \
--cc=kenneth.w.chen@intel.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=suresh.b.siddha@intel.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
Powered by JetHome