linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Ingo Molnar <mingo@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
	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: Wed, 13 Jul 2016 14:33:37 +0200	[thread overview]
Message-ID: <20160713123337.GY30909@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20160713122748.GC20253@khazad-dum.debian.net>

On Wed, Jul 13, 2016 at 09:27:48AM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 13 Jul 2016, Ingo Molnar wrote:
> > > 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.
> > 
> > That's more the natural 'direct' mapping from CPU internal topology to CPU id: 
> > what's close to each other physically is close to each other in the CPU id space 
> > as well.
> 
> But does it correctly reflect the hardware?  That seems to be the real
> question...

Its just enumeration afaict. But its weird that this changed. Some BIOS
team somewhere changed things and I want to know why (and how widespread
this is).

  reply	other threads:[~2016-07-13 12:34 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
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 [this message]
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=20160713123337.GY30909@twins.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=ak@linux.intel.com \
    --cc=hmh@hmh.eng.br \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mingo@kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).