linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Alex Shi <alex.shi@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: linux-mips@linux-mips.org, linux-ia64@vger.kernel.org,
	linux-sh@vger.kernel.org, dhowells@redhat.com, paulus@samba.org,
	hpa@zytor.com, sparclinux@vger.kernel.org, mingo@kernel.org,
	sivanich@sgi.com, x86@kernel.org, greg.pearson@hp.com,
	chris.mason@oracle.com, arjan.van.de.ven@intel.com,
	mattst88@gmail.com, pjt@google.com, fenghua.yu@intel.com,
	seto.hidetoshi@jp.fujitsu.com, cmetcalf@tilera.com,
	ak@linux.intel.com, ink@jurassic.park.msu.ru, anton@samba.org,
	tglx@linutronix.de, kamezawa.hiroyu@jp.fujitsu.com,
	rth@twiddle.net, tony.luck@intel.com,
	torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
	ralf@linux-mips.org, lethal@linux-sh.org,
	linux-alpha@vger.kernel.org, bob.picco@oracle.com,
	akpm@linux-foundation.org, linuxppc-dev@lists.ozlabs.org,
	davem@davemloft.net
Subject: Re: [RFC PATCH] sched/numa: do load balance between remote nodes
Date: Thu, 07 Jun 2012 08:33:28 +0800	[thread overview]
Message-ID: <4FCFF6D8.70507@intel.com> (raw)
In-Reply-To: <1338973295.2749.81.camel@twins>

On 06/06/2012 05:01 PM, Peter Zijlstra wrote:

> On Wed, 2012-06-06 at 14:52 +0800, Alex Shi wrote:
>> -       if (sched_domains_numa_distance[level] > REMOTE_DISTANCE)
>> +       if (sched_domains_numa_distance[level] > RECLAIM_DISTANCE) 
> 
> I actually considered this.. I just felt a little uneasy re-purposing
> the RECLAIM_DISTANCE for this, but I guess its all the same anyway. Both
> mean expensive-away-distance.
> 


I understand you, the BIOS guys don't have a good alignment with us on
this.

> So I've taken this.
> 
> thanks!

  reply	other threads:[~2012-06-07  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-06  6:52 [RFC PATCH] sched/numa: do load balance between remote nodes Alex Shi
2012-06-06  9:01 ` Peter Zijlstra
2012-06-07  0:33   ` Alex Shi [this message]
2012-06-06 10:53 ` Sergei Shtylyov

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=4FCFF6D8.70507@intel.com \
    --to=alex.shi@intel.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@samba.org \
    --cc=arjan.van.de.ven@intel.com \
    --cc=bob.picco@oracle.com \
    --cc=chris.mason@oracle.com \
    --cc=cmetcalf@tilera.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=fenghua.yu@intel.com \
    --cc=greg.pearson@hp.com \
    --cc=hpa@zytor.com \
    --cc=ink@jurassic.park.msu.ru \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=lethal@linux-sh.org \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mattst88@gmail.com \
    --cc=mingo@kernel.org \
    --cc=paulus@samba.org \
    --cc=pjt@google.com \
    --cc=ralf@linux-mips.org \
    --cc=rth@twiddle.net \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=sivanich@sgi.com \
    --cc=sparclinux@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).