From: Peter Williams <pwil3058@bigpond.net.au>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: Andrew Morton <akpm@osdl.org>, Con Kolivas <kernel@kolivas.org>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sched: modify move_tasks() to improve load balancing outcomes
Date: Tue, 18 Apr 2006 09:21:41 +1000 [thread overview]
Message-ID: <44442305.9010201@bigpond.net.au> (raw)
In-Reply-To: <20060417095920.A19931@unix-os.sc.intel.com>
Siddha, Suresh B wrote:
> On Sat, Apr 15, 2006 at 10:54:45AM +1000, Peter Williams wrote:
>> Yes, there are problems with the active/expired arrays but they're no
>>> The only special check in find_busiest_group() helping MT/MC balancing
>>> is pwr_now and pwr_move calculations..
>> What about the very messy code I had to put in so that
>> find_busiest_group() would return a group even if there were no queues
>> in the group with more than one task. Similar for find_busiest_queue().
>
> Thats messy for sure and that was introduced by you to fix an imabalance
> issue for a simple DP system(with out breaking HT systems). I will post a fix
> for that.
By moving the active load balance trigger out of load_balance() and
providing an independent trigger that does not require sub optimal
normal load balancing, I hope?
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
next prev parent reply other threads:[~2006-04-17 23:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-13 6:57 [PATCH] sched: modify move_tasks() to improve load balancing outcomes Peter Williams
2006-04-13 23:51 ` Siddha, Suresh B
2006-04-14 1:50 ` Peter Williams
2006-04-14 18:27 ` Siddha, Suresh B
2006-04-15 0:54 ` Peter Williams
2006-04-17 16:59 ` Siddha, Suresh B
2006-04-17 23:21 ` Peter Williams [this message]
2006-04-17 23:56 ` Peter Williams
2006-04-18 0:18 ` 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=44442305.9010201@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.