public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Jiri Olsa" <jolsa@kernel.org>,
	"Jean-Pierre Lozi" <jplozi@unice.fr>,
	"Jirka Hladky" <jhladky@redhat.com>,
	"Petr Surý" <psury@redhat.com>,
	lkml <linux-kernel@vger.kernel.org>,
	"Ingo Molnar" <mingo@kernel.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] x86/topology: Fallback to SMT level only once
Date: Mon, 29 Aug 2016 13:09:26 +0200	[thread overview]
Message-ID: <20160829110926.GB32481@krava> (raw)
In-Reply-To: <20160829104047.GH10153@twins.programming.kicks-ass.net>

On Mon, Aug 29, 2016 at 12:40:47PM +0200, Peter Zijlstra wrote:
> On Sun, Aug 28, 2016 at 08:19:46PM +0200, Jiri Olsa wrote:
> > Jirka, Peter and Jean-Pierre reported performance drop on
> > some cpus after making cpu offline and online again.
> > 
> > The reason is the kernel logic that falls back to SMT
> > level topology if more than one node is detected within
> > CPU package. During the system boot this logic cuts out
> > the DIE topology level and numa code adds NUMA level
> > on top of this.
> 
> Its not SMT topology, and back when I asked if he had CoD enabled or
> such he said not.
> 
> 
> See also:
> 
> http://lkml.kernel.org/r/1471559812-19967-3-git-send-email-srinivas.pandruvada@linux.intel.com
> 
> Arguably, that should have been split in two patches, but alas..

ok, that change will work for us as well

are you going to pull it?

thanks,
jirka

  reply	other threads:[~2016-08-29 11:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-28 18:19 [PATCH] x86/topology: Fallback to SMT level only once Jiri Olsa
2016-08-29 10:40 ` Peter Zijlstra
2016-08-29 11:09   ` Jiri Olsa [this message]
2016-08-29 12:20   ` Jirka Hladky

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=20160829110926.GB32481@krava \
    --to=jolsa@redhat.com \
    --cc=hpa@zytor.com \
    --cc=jhladky@redhat.com \
    --cc=jolsa@kernel.org \
    --cc=jplozi@unice.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=psury@redhat.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