From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Peter Williams <pwil3058@bigpond.net.au>
Cc: "Siddha, Suresh B" <suresh.b.siddha@intel.com>,
Andrew Morton <akpm@osdl.org>, Mike Galbraith <efault@gmx.de>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Ingo Molnar <mingo@elte.hu>, Con Kolivas <kernel@kolivas.org>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: smpnice loadbalancing with high priority tasks
Date: Sat, 1 Apr 2006 20:48:24 -0800 [thread overview]
Message-ID: <20060401204824.A8662@unix-os.sc.intel.com> (raw)
In-Reply-To: <442B3111.5030808@bigpond.net.au>; from pwil3058@bigpond.net.au on Thu, Mar 30, 2006 at 12:14:57PM +1100
Peter,
There are still issues which we need to address.. These are surfacing
as we are patching issue by issue(instead of addressing the root issue, which
is: presence of high priority tasks messes up load balancing of normal
priority tasks..)
for example
a) on a simple 4-way MP system, if we have one high priority and 4 normal
priority tasks, with smpnice we would like to see the high priority task
scheduled on one cpu, two other cpus getting one normal task each and the
fourth cpu getting the remaining two normal tasks. but with smpnice that
extra normal priority task keeps jumping from one cpu to another cpu having
the normal priority task.
This is because of the busiest_has_loaded_cpus, nr_loaded_cpus logic.. We
are not including the cpu with high priority task in max_load calculations
but including that in total and avg_load calcuations.. leading to max_load <
avg_load and load balance between cpus running normal priority tasks(2 Vs 1)
will always show imbalanace as one normal priority and the extra normal
priority task will keep moving from one cpu to another cpu having
normal priority task..
b) on a simple DP system, if we have two high priority and two normal priority
tasks, ideally we should schedule one high and one normal priority task on
each cpu.. current code doesn't find an imbalance if both the normal priority
tasks gets scheduled on the same cpu(running one high priority task)
there may not be benchmarks which expose these conditions.. but I think
we haven't addressed the corner case conditions well enough..
thanks,
suresh
next prev parent reply other threads:[~2006-04-02 4:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-28 6:00 [PATCH] sched: smpnice work around for active_load_balance() Peter Williams
2006-03-28 19:25 ` Siddha, Suresh B
2006-03-28 22:44 ` Peter Williams
2006-03-29 2:14 ` Peter Williams
2006-03-29 2:52 ` Siddha, Suresh B
2006-03-29 3:42 ` Peter Williams
2006-03-29 22:52 ` Siddha, Suresh B
2006-03-29 23:40 ` Peter Williams
2006-03-30 0:50 ` Siddha, Suresh B
2006-03-30 1:14 ` Peter Williams
2006-04-02 4:48 ` Siddha, Suresh B [this message]
2006-04-02 7:08 ` smpnice loadbalancing with high priority tasks Peter Williams
2006-04-04 0:24 ` Siddha, Suresh B
2006-04-04 1:22 ` Peter Williams
2006-04-04 1:34 ` Peter Williams
2006-04-04 2:11 ` Siddha, Suresh B
2006-04-04 3:24 ` Peter Williams
2006-04-04 4:34 ` Peter Williams
2006-04-06 2:14 ` Peter Williams
2006-04-20 1:24 ` [patch] smpnice: don't consider sched groups which are lightly loaded for balancing Siddha, Suresh B
2006-04-20 5:19 ` Peter Williams
2006-04-20 16:54 ` Siddha, Suresh B
2006-04-20 23:11 ` Peter Williams
2006-04-20 23:49 ` Andrew Morton
2006-04-21 0:25 ` Siddha, Suresh B
2006-04-21 0:28 ` Peter Williams
2006-04-21 1:25 ` Andrew Morton
2006-04-20 17:04 ` Siddha, Suresh B
2006-04-21 0:00 ` Peter Williams
2006-04-03 1:04 ` [PATCH] sched: smpnice work around for active_load_balance() Peter Williams
2006-04-03 16:57 ` Siddha, Suresh B
2006-04-03 23:11 ` Peter Williams
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=20060401204824.A8662@unix-os.sc.intel.com \
--to=suresh.b.siddha@intel.com \
--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=pwil3058@bigpond.net.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