From: Borislav Petkov <bp@alien8.de>
To: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>
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:43:59 +0100 [thread overview]
Message-ID: <20170202154359.fevz4fmwc6t4ew75@pd.tnic> (raw)
In-Reply-To: <20170202121054.im3c3iiqp26a2dyb@pd.tnic>
On Thu, Feb 02, 2017 at 01:10:54PM +0100, Borislav Petkov wrote:
> Now on to run the same thing on a bigger bulldozer.
It looks differently on the bigger box:
before:
Performance counter stats for 'make -s -j17 bzImage' (3 runs):
1333240.579196 task-clock (msec) # 9.271 CPUs utilized ( +- 0.03% )
393,521 context-switches # 0.295 K/sec ( +- 0.27% )
6,629,632,543 cache-misses ( +- 0.10% )
51,570 cpu-migrations # 0.039 K/sec ( +- 1.21% )
27,812,379 page-faults # 0.021 M/sec ( +- 0.05% )
3,633,456,270,448 cycles # 2.725 GHz ( +- 0.03% )
2,144,192,888,087 instructions # 0.59 insn per cycle ( +- 0.00% )
476,225,081,234 branches # 357.194 M/sec ( +- 0.00% )
25,294,199,758 branch-misses # 5.31% of all branches ( +- 0.02% )
143.807894000 seconds time elapsed ( +- 0.89% )
after:
Performance counter stats for 'make -s -j17 bzImage' (3 runs):
1330842.218684 task-clock (msec) # 9.047 CPUs utilized ( +- 0.14% )
396,044 context-switches # 0.298 K/sec ( +- 0.60% )
6,625,112,597 cache-misses ( +- 0.36% )
60,050 cpu-migrations # 0.045 K/sec ( +- 1.11% )
27,862,451 page-faults # 0.021 M/sec ( +- 0.08% )
3,625,822,644,429 cycles # 2.724 GHz ( +- 0.12% )
2,144,932,865,362 instructions # 0.59 insn per cycle ( +- 0.01% )
476,375,898,692 branches # 357.951 M/sec ( +- 0.01% )
25,226,837,830 branch-misses # 5.30% of all branches ( +- 0.09% )
147.109189694 seconds time elapsed ( +- 0.49% )
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2017-02-02 15:44 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 [this message]
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
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=20170202154359.fevz4fmwc6t4ew75@pd.tnic \
--to=bp@alien8.de \
--cc=Brice.Goglin@inria.fr \
--cc=Yazen.Ghannam@amd.com \
--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).