From: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: x86-ml <x86@kernel.org>, Yves Dionne <yves.dionne@gmail.com>,
Brice Goglin <Brice.Goglin@inria.fr>,
Peter Zijlstra <peterz@infradead.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: RE: [RFC PATCH] x86/CPU/AMD: Bring back Compute Unit ID
Date: Thu, 2 Feb 2017 16:14:54 +0000 [thread overview]
Message-ID: <CY4PR12MB164014100E42E4970B846B18F84C0@CY4PR12MB1640.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20170202121054.im3c3iiqp26a2dyb@pd.tnic>
> -----Original Message-----
> From: Borislav Petkov [mailto:bp@alien8.de]
> Sent: Thursday, February 2, 2017 7:11 AM
>
> Context switches have dropped, cache misses are the same and we have a
> rise in cpu-migrations. That last bit is interesting and I don't have an
> answer yet. Maybe peterz has an idea.
>
Could it be that the scheduler is more lax about migrations between SMT
siblings?
> Cycles have dropped too.
>
> And we're 6 secs faster so I'll take that.
>
> Now on to run the same thing on a bigger bulldozer.
>
Here are my results on a 32C Bulldozer system with an SSD. Also, I use ccache so
I added "ccache -C" in the pre-build script so the cache gets cleared.
Before:
Performance counter stats for 'make -s -j65 bzImage' (3 runs):
2375752.777479 task-clock (msec) # 23.589 CPUs utilized ( +- 0.35% )
1,198,979 context-switches # 0.505 K/sec ( +- 0.34% )
8,964,671,259 cache-misses ( +- 0.44% )
79,399 cpu-migrations # 0.033 K/sec ( +- 1.92% )
37,840,875 page-faults # 0.016 M/sec ( +- 0.20% )
5,425,612,846,538 cycles # 2.284 GHz ( +- 0.36% )
3,367,750,745,825 instructions # 0.62 insn per cycle ( +- 0.11% )
750,591,286,261 branches # 315.938 M/sec ( +- 0.11% )
43,544,059,077 branch-misses # 5.80% of all branches ( +- 0.08% )
100.716043494 seconds time elapsed ( +- 1.97% )
After:
Performance counter stats for 'make -s -j65 bzImage' (3 runs):
1736720.488346 task-clock (msec) # 23.529 CPUs utilized ( +- 0.16% )
1,144,737 context-switches # 0.659 K/sec ( +- 0.20% )
8,570,352,975 cache-misses ( +- 0.33% )
91,817 cpu-migrations # 0.053 K/sec ( +- 1.67% )
37,688,118 page-faults # 0.022 M/sec ( +- 0.03% )
5,547,082,899,245 cycles # 3.194 GHz ( +- 0.19% )
3,363,365,420,405 instructions # 0.61 insn per cycle ( +- 0.00% )
749,676,420,820 branches # 431.662 M/sec ( +- 0.00% )
43,243,046,270 branch-misses # 5.77% of all branches ( +- 0.01% )
73.810517234 seconds time elapsed ( +- 0.02% )
Thanks,
Yazen
next prev parent reply other threads:[~2017-02-02 16:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 20:02 [RFC PATCH] x86/CPU/AMD: Bring back Compute Unit ID Borislav Petkov
2017-02-01 21:37 ` Ghannam, Yazen
2017-02-01 21:44 ` Borislav Petkov
2017-02-01 21:55 ` Ghannam, Yazen
2017-02-01 22:25 ` Borislav Petkov
2017-02-01 22:41 ` Borislav Petkov
2017-02-02 12:10 ` Borislav Petkov
2017-02-02 15:43 ` Borislav Petkov
2017-02-02 16:09 ` Ingo Molnar
2017-02-02 17:04 ` Borislav Petkov
2017-02-02 18:10 ` Borislav Petkov
2017-02-02 20:45 ` Ghannam, Yazen
2017-02-02 16:14 ` Ghannam, Yazen [this message]
2017-02-02 16:29 ` Ingo Molnar
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=CY4PR12MB164014100E42E4970B846B18F84C0@CY4PR12MB1640.namprd12.prod.outlook.com \
--to=yazen.ghannam@amd.com \
--cc=Brice.Goglin@inria.fr \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
--cc=yves.dionne@gmail.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;
as well as URLs for NNTP newsgroup(s).