From: Mike Galbraith <efault@gmx.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Suresh Siddha <suresh.b.siddha@intel.com>,
Paul Turner <pjt@google.com>,
Arjan Van De Ven <arjan@linux.intel.com>,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: [rfc][patch] select_idle_sibling() inducing bouncing on westmere
Date: Sat, 26 May 2012 10:27:14 +0200 [thread overview]
Message-ID: <1338020834.7747.8.camel@marge.simpson.net> (raw)
In-Reply-To: <1338017364.14636.9.camel@twins>
On Sat, 2012-05-26 at 09:29 +0200, Peter Zijlstra wrote:
> On Sat, 2012-05-26 at 08:37 +0200, Mike Galbraith wrote:
>
> > Ew. 3.4 went broke for Q6600, and performance went... far far away.
> >
> > [ 0.200057] CPU0 attaching sched-domain:
> > [ 0.204016] domain 0: span 0-3 level MC
> > [ 0.208015] groups: 0 1 2 3
> > [ 0.210970] CPU1 attaching sched-domain:
> > [ 0.212014] domain 0: span 0-3 level MC
> > [ 0.216016] groups: 1 2 3 0
> > [ 0.220016] CPU2 attaching sched-domain:
> > [ 0.224015] domain 0: span 0-3 level MC
> > [ 0.228016] groups: 2 3 0 1
> > [ 0.232015] CPU3 attaching sched-domain:
> > [ 0.236016] domain 0: span 0-3 level MC
> > [ 0.240017] groups: 3 0 1 2
>
>
> Oh yikes, I guess I wrecked
> arch/x86/kernel/smpboot.c:cpu_coregroup_mask() in
> 8e7fbcbc22c12414bcc9dfdd683637f58fb32759.
>
> That should very much always return llc mask, I just got that AMD case
> confused. It looks like it should look like:
>
>
> const struct cpumask *cpu_coregroup_mask(int cpu)
> {
> return cpu_llc_mask(cpu);
> }
All better.
Too bad 'enterprise dude' turned cpuhog at 3.0, 'silly tester guy' would
have spotted this instantly. Hohum, back to finding out what happened
to cpufreq.
[ 0.212062] CPU0 attaching sched-domain:
[ 0.216016] domain 0: span 0-1 level MC
[ 0.220013] groups: 0 1
[ 0.222664] domain 1: span 0-3 level CPU
[ 0.225754] groups: 0-1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
[ 0.233859] CPU1 attaching sched-domain:
[ 0.236015] domain 0: span 0-1 level MC
[ 0.241673] groups: 1 0
[ 0.244385] domain 1: span 0-3 level CPU
[ 0.248016] groups: 0-1 (cpu_power = 2048) 2-3 (cpu_power = 2048)
[ 0.254219] CPU2 attaching sched-domain:
[ 0.256016] domain 0: span 2-3 level MC
[ 0.261673] groups: 2 3
[ 0.264578] domain 1: span 0-3 level CPU
[ 0.268016] groups: 2-3 (cpu_power = 2048) 0-1 (cpu_power = 2048)
[ 0.276020] CPU3 attaching sched-domain:
[ 0.279929] domain 0: span 2-3 level MC
[ 0.281675] groups: 3 2
[ 0.284577] domain 1: span 0-3 level CPU
[ 0.289764] groups: 2-3 (cpu_power = 2048) 0-1 (cpu_power = 2048)
next prev parent reply other threads:[~2012-05-26 8:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 11:04 Mike Galbraith
2012-05-24 13:17 ` Peter Zijlstra
2012-05-24 13:20 ` Peter Zijlstra
2012-05-25 6:14 ` Mike Galbraith
2012-05-26 6:37 ` Mike Galbraith
2012-05-26 7:29 ` Peter Zijlstra
2012-05-26 8:27 ` Mike Galbraith [this message]
2012-05-27 9:17 ` Mike Galbraith
2012-05-27 11:02 ` Mike Galbraith
2012-05-27 11:12 ` Mike Galbraith
2012-05-27 14:11 ` Arjan van de Ven
2012-05-27 14:29 ` Mike Galbraith
2012-05-27 14:32 ` Mike Galbraith
2012-05-29 18:58 ` Andreas Herrmann
2012-05-25 6:08 ` Mike Galbraith
2012-05-25 8:06 ` Mike Galbraith
2012-06-05 14:30 ` Mike Galbraith
2012-06-11 16:57 ` [patch v3] sched: fix select_idle_sibling() induced bouncing Mike Galbraith
2012-06-11 17:22 ` Peter Zijlstra
2012-06-11 17:55 ` Mike Galbraith
2012-06-11 18:53 ` Suresh Siddha
2012-06-12 3:18 ` Mike Galbraith
2012-06-20 10:48 ` [tip:sched/core] sched: Improve scalability via 'CPU buddies', which withstand random perturbations tip-bot for Mike Galbraith
2012-07-24 14:18 ` tip-bot for Mike Galbraith
2012-06-19 8:47 ` [patch v3] sched: fix select_idle_sibling() induced bouncing Paul Turner
2012-06-06 10:17 ` [rfc][patch] select_idle_sibling() inducing bouncing on westmere Mike Galbraith
2012-06-06 10:38 ` Mike Galbraith
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=1338020834.7747.8.camel@marge.simpson.net \
--to=efault@gmx.de \
--cc=andreas.herrmann3@amd.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--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
Powered by JetHome