From: Peter Zijlstra <peterz@infradead.org>
To: Jirka Hladky <jhladky@redhat.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Kamil Kolakowski <kkolakow@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Jean-Pierre Lozi <jplozi@unice.fr>,
Alexandra Fedorova <sasha@ece.ubc.ca>,
Baptiste Lepers <baptiste.lepers@gmail.com>
Subject: Re: Kernel v4.7-rc5 - performance degradation upto 40% after disabling and re-enabling a core
Date: Wed, 29 Jun 2016 11:58:24 +0200 [thread overview]
Message-ID: <20160629095824.GW30921@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <CAE4VaGBO0soGf0pfdduxmuAxU5hCN3grha8DOa5HEgT5Lt9HVQ@mail.gmail.com>
On Wed, Jun 29, 2016 at 11:47:56AM +0200, Jirka Hladky wrote:
> Hi Peter,
>
> I think Cluster on Die technology was introduced in Haswell generation. The
> server I'm using is equipped with 4x Intel E5-4610 v2 (Ivy Bridge). I have
> double checked the BIOS and there is no cluster on die setting.
Oh right, that's E5v3..
> The authors of the paper have reported the issue on AMD Bulldozer CPU which
> also does not have COD technology.
The Opteron 6272, which they use, is an Interlagos, that has something
similar in that each package contains two nodes.
And their patch touches exactly that part of the x86 topo setup, the
match_die() && !same_node() condition, IOW same package, different node.
That's not a path an Intel chip would trigger without COD support.
next prev parent reply other threads:[~2016-06-29 9:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 23:15 Jirka Hladky
2016-06-29 8:46 ` Peter Zijlstra
[not found] ` <CAE4VaGBO0soGf0pfdduxmuAxU5hCN3grha8DOa5HEgT5Lt9HVQ@mail.gmail.com>
2016-06-29 9:58 ` Peter Zijlstra [this message]
2016-07-12 9:04 ` Jirka Hladky
2016-07-28 21:48 ` 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=20160629095824.GW30921@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=baptiste.lepers@gmail.com \
--cc=jhladky@redhat.com \
--cc=jplozi@unice.fr \
--cc=kkolakow@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=sasha@ece.ubc.ca \
/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
all inboxes | Powered by JetHome®