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>,
"Chen, Kenneth W" <kenneth.w.chen@intel.com>,
Con Kolivas <kernel@kolivas.org>, 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: move enough load to balance average load per task
Date: Mon, 10 Apr 2006 22:47:09 -0700 [thread overview]
Message-ID: <20060410224709.A28321@unix-os.sc.intel.com> (raw)
In-Reply-To: <443B0CF8.6060707@bigpond.net.au>; from pwil3058@bigpond.net.au on Tue, Apr 11, 2006 at 11:57:12AM +1000
On Tue, Apr 11, 2006 at 11:57:12AM +1000, Peter Williams wrote:
> Siddha, Suresh B wrote:
> > Can you give an example scenario where this patch helps? And doesn't
> > the normal imabalance calculations capture those issues?
>
> Yes, I think that the normal imbalance calculations (in
> find_busiest_queue()) will generally capture the aim of having
> approximately equal average loads per task on run queues. But this bit
> of code is a special case in that the extra aggression being taken by
> the load balancer (in response to a scenario raised by you) is being
Can you give a specific example which shows the problem
and which you are trying to fix with this particular patch..
thanks,
suresh
next prev parent reply other threads:[~2006-04-11 5:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 6:45 Peter Williams
2006-04-11 1:12 ` Siddha, Suresh B
2006-04-11 1:57 ` Peter Williams
2006-04-11 5:47 ` Siddha, Suresh B [this message]
2006-04-11 23:46 ` Peter Williams
2006-04-12 1:57 ` Siddha, Suresh B
2006-04-12 5:06 ` Peter Williams
2006-04-12 16:55 ` Siddha, Suresh B
2006-04-12 23:13 ` Peter Williams
[not found] ` <443D95DF.2090807@bigpond.net.au>
2006-04-14 0:31 ` smpnice: issues with finding busiest queue Siddha, Suresh B
2006-04-14 1:17 ` 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=20060410224709.A28321@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
Powered by JetHome