public inbox for linuxppc-dev@ozlabs.org 
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello•nl>
To: Alex Shi <alex.shi@intel•com>
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: Wed, 06 Jun 2012 11:01:35 +0200	[thread overview]
Message-ID: <1338973295.2749.81.camel@twins> (raw)
In-Reply-To: <1338965571-9812-1-git-send-email-alex.shi@intel.com>

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)=20

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.

So I've taken this.

thanks!

  reply	other threads:[~2012-06-06  9:02 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 [this message]
2012-06-07  0:33   ` Alex Shi
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=1338973295.2749.81.camel@twins \
    --to=a.p.zijlstra@chello$(echo .)nl \
    --cc=ak@linux$(echo .)intel.com \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=alex.shi@intel$(echo .)com \
    --cc=anton@samba$(echo .)org \
    --cc=arjan.van.de.ven@intel$(echo .)com \
    --cc=bob.picco@oracle$(echo .)com \
    --cc=chris.mason@oracle$(echo .)com \
    --cc=cmetcalf@tilera$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=dhowells@redhat$(echo .)com \
    --cc=fenghua.yu@intel$(echo .)com \
    --cc=greg.pearson@hp$(echo .)com \
    --cc=hpa@zytor$(echo .)com \
    --cc=ink@jurassic$(echo .)park.msu.ru \
    --cc=kamezawa.hiroyu@jp$(echo .)fujitsu.com \
    --cc=lethal@linux-sh$(echo .)org \
    --cc=linux-alpha@vger$(echo .)kernel.org \
    --cc=linux-ia64@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-mips@linux-mips$(echo .)org \
    --cc=linux-sh@vger$(echo .)kernel.org \
    --cc=linuxppc-dev@lists$(echo .)ozlabs.org \
    --cc=mattst88@gmail$(echo .)com \
    --cc=mingo@kernel$(echo .)org \
    --cc=paulus@samba$(echo .)org \
    --cc=pjt@google$(echo .)com \
    --cc=ralf@linux-mips$(echo .)org \
    --cc=rth@twiddle$(echo .)net \
    --cc=seto.hidetoshi@jp$(echo .)fujitsu.com \
    --cc=sivanich@sgi$(echo .)com \
    --cc=sparclinux@vger$(echo .)kernel.org \
    --cc=tglx@linutronix$(echo .)de \
    --cc=tony.luck@intel$(echo .)com \
    --cc=torvalds@linux-foundation$(echo .)org \
    --cc=x86@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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