From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: kernel@kolivas.org
Cc: mingo@elte.hu, nickpiggin@yahoo.com.au, linux-kernel@vger.kernel.org
Subject: smp 'nice' bias support breaks scheduler behavior
Date: Thu, 26 Jan 2006 02:52:21 -0800 [thread overview]
Message-ID: <20060126025220.B8521@unix-os.sc.intel.com> (raw)
Con,
> [PATCH] sched: implement nice support across physical cpus on SMP
I don't see imbalance calculations in find_busiest_group() take
prio_bias into account. This will result in wrong imbalance value and
will cause issues.
For example on a DP system with HT, if there are three runnable processes
(simple infinite loop with same nice value), this patch is resulting in bouncing
of these 3 processes from one processor to another...Lets assume
if the 3 processes are scheduled as 2 in package-0 and 1 in package1..
Now when the busy processor on package-1 does load balance and as
imbalance doesn't take "prio_bias" into account, this will kick active
load balance on package-0.. And this is continuing for ever, resulting
in bouncing from one processor to another.
Even when the system is completely loaded and if there is an imbalance,
this patch causes wrong imabalance counts and cause unoptimized
movements.
Do you want to look into this and post a patch for 2.6.16?
thanks,
suresh
next reply other threads:[~2006-01-26 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-26 10:52 Siddha, Suresh B [this message]
2006-01-26 12:25 ` smp 'nice' bias support breaks scheduler behavior Con Kolivas
2006-01-26 23:36 ` Peter Williams
2006-01-26 23:56 ` Siddha, Suresh B
2006-01-27 1:29 ` Con Kolivas
2006-01-27 1:34 ` Siddha, Suresh B
2006-01-27 1:54 ` Con Kolivas
2006-01-27 2:11 ` Siddha, Suresh B
2006-01-27 2:58 ` Con Kolivas
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=20060126025220.B8521@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--cc=kernel@kolivas.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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