From: Sergei Shtylyov <sshtylyov@mvista.com>
To: Alex Shi <alex.shi@intel.com>
Cc: a.p.zijlstra@chello.nl, anton@samba.org,
benh@kernel.crashing.org, cmetcalf@tilera.com,
dhowells@redhat.com, davem@davemloft.net, fenghua.yu@intel.com,
hpa@zytor.com, ink@jurassic.park.msu.ru,
linux-alpha@vger.kernel.org, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@linux-mips.org,
linuxppc-dev@lists.ozlabs.org, linux-sh@vger.kernel.org,
mattst88@gmail.com, paulus@samba.org, lethal@linux-sh.org,
ralf@linux-mips.org, rth@twiddle.net, sparclinux@vger.kernel.org,
tony.luck@intel.com, x86@kernel.org, sivanich@sgi.com,
greg.pearson@hp.com, kamezawa.hiroyu@jp.fujitsu.com,
bob.picco@oracle.com, chris.mason@oracle.com,
torvalds@linux-foundation.org, akpm@linux-foundation.org,
mingo@kernel.org, pjt@google.com, tglx@linutronix.de,
seto.hidetoshi@jp.fujitsu.com, ak@linux.intel.com,
arjan.van.de.ven@intel.com
Subject: Re: [RFC PATCH] sched/numa: do load balance between remote nodes
Date: Wed, 06 Jun 2012 10:53:08 +0000 [thread overview]
Message-ID: <4FCF3694.206@mvista.com> (raw)
In-Reply-To: <1338965571-9812-1-git-send-email-alex.shi@intel.com>
Hello.
On 06-06-2012 10:52, Alex Shi wrote:
> commit cb83b629b
Please also specify that commit's summary in parens.
> remove the NODE sched domain and check if the node
> distance in SLIT table is farther than REMOTE_DISTANCE, if so, it will
> lose the load balance chance at exec/fork/wake_affine points.
> But actually, even the node distance is farther than REMOTE_DISTANCE,
> Modern CPUs also has QPI like connections, that make memory access is
"Is" not needed here.
> not too slow between nodes. So above losing on NUMA machine make a
> huge performance regression on benchmark: hackbench, tbench, netperf
> and oltp etc.
> This patch will recover the scheduler behavior to old mode on all my
> Intel platforms: NHM EP/EX, WSM EP, SNB EP/EP4S, and so remove the
> perfromance regressions. (all of them just has 2 kinds distance, 10 21)
> Signed-off-by: Alex Shi<alex.shi@intel.com>
WBR, Sergei
prev parent reply other threads:[~2012-06-06 10:53 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
2012-06-06 10:53 ` Sergei Shtylyov [this message]
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=4FCF3694.206@mvista.com \
--to=sshtylyov@mvista.com \
--cc=a.p.zijlstra@chello.nl \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@intel.com \
--cc=anton@samba.org \
--cc=arjan.van.de.ven@intel.com \
--cc=benh@kernel.crashing.org \
--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).