public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: paulmck@linux.vnet.ibm.com, tglx@linutronix.de, mingo@elte.hu,
	ak@linux.intel.com, linux-kernel@vger.kernel.org
Subject: Re: Odd performance results
Date: Tue, 12 Jul 2016 20:51:20 +0200	[thread overview]
Message-ID: <20160712185120.GX30909@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <27d2c710-479d-77a9-f2c6-875e9c2bc40f@zytor.com>

On Tue, Jul 12, 2016 at 10:49:58AM -0700, H. Peter Anvin wrote:
> On 07/12/16 08:05, Paul E. McKenney wrote:
> The CPU in question (and /proc/cpuinfo should show this) has four cores
> with a total of eight threads.  The "siblings" and "cpu cores" fields in
> /proc/cpuinfo should show the same thing.  So I am utterly confused
> about what is unexpected here?

Typically threads are enumerated differently on Intel parts. Namely:

	cpu_id = code_id + nr_cores * smt_id

which gives, for a 4 core, 2 thread part:

	0-3: core 0-3, smt0
	4-7: core 0-3, smt1

My Core i7-2600k for example has:

$ cat /sys/devices/system/cpu/cpu*/topology/thread_siblings_list
0,4
1,5
2,6
3,7
0,4
1,5
2,6
3,7

The ordering Paul has, namely 0,1 for core0,smt{0,1} is not something
I've ever seen on an Intel part. AMD otoh does enumerate their CMT stuff
like what Paul has.

  parent reply	other threads:[~2016-07-12 18:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-10  4:26 Odd performance results Paul E. McKenney
2016-07-10  5:17 ` Peter Zijlstra
2016-07-10 14:43   ` Paul E. McKenney
2016-07-12 14:55     ` Peter Zijlstra
2016-07-12 15:05       ` Paul E. McKenney
2016-07-12 17:49         ` H. Peter Anvin
2016-07-12 18:26           ` Paul E. McKenney
2016-07-12 18:51           ` Peter Zijlstra [this message]
2016-07-12 19:10             ` [CRM114spam]: " Dr. David Alan Gilbert
2016-07-12 19:59               ` Paul E. McKenney
2016-07-13  7:20                 ` Ingo Molnar
2016-07-13  7:18             ` Ingo Molnar
2016-07-13 12:27               ` Henrique de Moraes Holschuh
2016-07-13 12:33                 ` Peter Zijlstra
2016-07-13 14:06               ` Paul E. McKenney

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=20160712185120.GX30909@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=tglx@linutronix.de \
    /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