From: Peter Zijlstra <peterz@infradead.org>
To: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
jaswinder@kernel.org, jaswinderrajput@gmail.com,
tglx@linutronix.de, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [tip:perfcounters/urgent] perf stat: Improve output
Date: Mon, 29 Jun 2009 19:11:31 +0200 [thread overview]
Message-ID: <1246295491.17061.43.camel@laptop> (raw)
In-Reply-To: <tip-6e750a8fc009fd0ae98704525d1d8e80d60e8cc9@git.kernel.org>
On Sat, 2009-06-27 at 17:31 +0000, tip-bot for Jaswinder Singh Rajput
wrote:
> Before:
> 150708 L1-d$-stores (scaled from 23.57%)
> 428804 L1-d$-prefetches (scaled from 23.47%)
> 314446 L1-d$-prefetch-misses (scaled from 23.42%)
> 252626137 L1-i$-loads (scaled from 23.24%)
> 5297550 dTLB-load-misses (scaled from 23.96%)
> 106992392 branch-loads (scaled from 23.67%)
> 5239561 branch-load-misses (scaled from 23.43%)
>
> After:
> 1731713 L1-d$-loads ( 14.25x scaled)
> 44241 L1-d$-prefetches ( 3.88x scaled)
> 21076 L1-d$-prefetch-misses ( 3.40x scaled)
> 5789421 L1-i$-loads ( 3.78x scaled)
> 29645 dTLB-load-misses ( 2.95x scaled)
> 461474 branch-loads ( 6.52x scaled)
> 7493 branch-load-misses ( 26.57x scaled)
I really rather like the before better. Its far easier to get a feel for
the overload factor from a fraction that from this multiplier.
next prev parent reply other threads:[~2009-06-29 17:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 21:30 [GIT PULL -tip][PATCH 0/3 -tip] perf stat patches Jaswinder Singh Rajput
2009-06-26 21:32 ` [PATCH 1/3 -tip] perf stat: fix stat output Jaswinder Singh Rajput
2009-06-26 21:33 ` [PATCH 2/3 -tip] perf_counter tools: Add support to set of multiple events in one shot Jaswinder Singh Rajput
2009-06-26 21:35 ` [PATCH 3/3 -tip] perf_counter tools: Add support for all CACHE events Jaswinder Singh Rajput
2009-06-27 16:38 ` [PATCH 2/3 -tip] perf_counter tools: Add support to set of multiple events in one shot Ingo Molnar
2009-06-27 19:04 ` Jaswinder Singh Rajput
2009-06-28 13:29 ` Ingo Molnar
2009-06-28 15:16 ` Jaswinder Singh Rajput
2009-06-29 3:57 ` Ingo Molnar
2009-06-30 8:38 ` Jaswinder Singh Rajput
2009-06-30 9:57 ` Ingo Molnar
2009-06-30 13:22 ` Jaswinder Singh Rajput
2009-06-30 22:47 ` Ingo Molnar
2009-06-27 17:31 ` [tip:perfcounters/urgent] perf stat: Improve output tip-bot for Jaswinder Singh Rajput
2009-06-29 17:11 ` Peter Zijlstra [this message]
2009-06-29 19:52 ` 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=1246295491.17061.43.camel@laptop \
--to=peterz@infradead.org \
--cc=hpa@zytor.com \
--cc=jaswinder@kernel.org \
--cc=jaswinderrajput@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--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