public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <nickpiggin@yahoo.com.au>
To: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
Cc: Ingo Molnar <mingo@elte.hu>, akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch] sched: fix active load balance
Date: Thu, 14 Apr 2005 09:06:50 +1000	[thread overview]
Message-ID: <425DA60A.4090208@yahoo.com.au> (raw)
In-Reply-To: <20050413132833.B25137@unix-os.sc.intel.com>

Siddha, Suresh B wrote:
> On Wed, Apr 13, 2005 at 10:08:28PM +0200, Ingo Molnar wrote:
> 
>>* Siddha, Suresh B <suresh.b.siddha@intel.com> wrote:
>>
>>
>>>-	for_each_domain(target_cpu, sd) {
>>>+	for_each_domain(target_cpu, sd)
>>> 		if ((sd->flags & SD_LOAD_BALANCE) &&
>>>-			cpu_isset(busiest_cpu, sd->span)) {
>>>-				sd = tmp;
>>>+			cpu_isset(busiest_cpu, sd->span))
>>> 				break;
>>>-		}
>>>-	}
>>

Yep that was broken :(
Thanks for picking that up Suresh.

>>hm, the right fix i think is to do:
>>
>> 	for_each_domain(target_cpu, tmp) {
>>  		if ((tmp->flags & SD_LOAD_BALANCE) &&
>> 			cpu_isset(busiest_cpu, tmp->span)) {
>> 				sd = tmp;
>>  				break;
>> 		}
>> 	}
> 
> 
> Your suggestion also looks similar to my patch. You are also breaking on the 
> first one.
> 
> 
>>because when balancing we want to match the widest-scope domain, not the 
>>first one.
> 
> 
> We want the first domain spanning both the cpu's. That is the domain where
> normal load balance failed and we restore to active load balance.
> 

Yes, that's right.

-- 
SUSE Labs, Novell Inc.


  reply	other threads:[~2005-04-13 23:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-13 19:07 [patch] sched: fix active load balance Siddha, Suresh B
2005-04-13 20:08 ` Ingo Molnar
2005-04-13 20:28   ` Siddha, Suresh B
2005-04-13 23:06     ` Nick Piggin [this message]
2005-04-14  7:23     ` Ingo Molnar

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=425DA60A.4090208@yahoo.com.au \
    --to=nickpiggin@yahoo.com.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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