From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Roland Dreier <rdreier@cisco.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip] perf_counter tools: shorten names for events
Date: Fri, 26 Jun 2009 21:36:39 +0530 [thread overview]
Message-ID: <1246032399.3063.3.camel@hpdv5.satnam> (raw)
In-Reply-To: <20090625153406.GA12918@elte.hu>
On Thu, 2009-06-25 at 17:34 +0200, Ingo Molnar wrote:
> * Roland Dreier <rdreier@cisco.com> wrote:
>
> > > 266590464 L1d-loads (scaled from 23.03%)
> >
> > IMHO "L1d" is too abbreviated for it to be obvious that it means
> > L1 data cache. If you want something really short maybe "L1-d$"
> > might be a little clearer, but I stil like "L1-dcache" best.
>
> i changed it to L1-d$ / L1-i$.
>
> > The formatting of aligning things is nice defitely but we could
> > also shorten lines by saying "scaled from" in fewer characters
> > maybe? (I have to admit I don't know what "scaled from X%" means
> > in this case so I can't suggest something better, but the fact
> > that I can't easily tell what it means probably suggests that the
> > wording could be improved)
>
> Indeed, the '(scaled from 12.3%)' message should i guess be changed
> to:
>
> (9.43x scaled)
>
> ( and a multiplicative factor is more expressive anyway, than the
> percentage of from where we scale up. )
>
Can you please let me know how you get 9.43x from 12.3%
Thanks,
--
JSR
next prev parent reply other threads:[~2009-06-26 16:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 12:28 Jaswinder Singh Rajput
2009-06-23 13:52 ` Jaswinder Singh Rajput
2009-06-23 19:56 ` Ingo Molnar
2009-06-23 22:12 ` Jaswinder Singh Rajput
2009-06-23 22:59 ` Jaswinder Singh Rajput
2009-06-24 8:40 ` Ingo Molnar
2009-06-24 17:59 ` Jaswinder Singh Rajput
2009-06-24 18:07 ` Ingo Molnar
2009-06-24 18:18 ` Jaswinder Singh Rajput
2009-06-24 20:41 ` Jaswinder Singh Rajput
2009-06-24 21:00 ` Thomas Gleixner
2009-06-25 4:29 ` Jaswinder Singh Rajput
2009-06-25 4:34 ` Roland Dreier
2009-06-25 9:22 ` Ingo Molnar
2009-06-25 9:24 ` Ingo Molnar
2009-06-25 12:48 ` Thomas Gleixner
2009-06-25 13:23 ` Jaswinder Singh Rajput
2009-06-25 15:05 ` Roland Dreier
2009-06-25 15:11 ` Jaswinder Singh Rajput
2009-06-25 15:03 ` Roland Dreier
2009-06-25 15:24 ` Ingo Molnar
2009-06-25 9:33 ` Ingo Molnar
2009-06-25 12:55 ` Jaswinder Singh Rajput
2009-06-25 15:09 ` Roland Dreier
2009-06-25 15:26 ` Ingo Molnar
2009-06-25 15:34 ` Ingo Molnar
2009-06-26 16:06 ` Jaswinder Singh Rajput [this message]
2009-06-26 18:47 ` Ingo Molnar
2009-07-05 0:25 ` Anton Blanchard
2009-07-05 0:32 ` Ingo Molnar
2009-07-06 12:01 ` [PATCH] perf_counter tools: Rename cache events to remove $ Anton Blanchard
2009-07-10 10:39 ` [tip:perfcounters/core] " tip-bot for Anton Blanchard
2009-06-25 15:33 ` [tip:perfcounters/urgent] perf_counter tools: Shorten names for events tip-bot for Jaswinder Singh Rajput
2009-06-25 15:57 ` Jaswinder Singh Rajput
2009-06-25 19:55 ` Ingo Molnar
2009-06-25 19:57 ` [tip:perfcounters/urgent] perf_counter tools: Add alias for 'l1d' and 'l1i' tip-bot for Jaswinder Singh Rajput
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=1246032399.3063.3.camel@hpdv5.satnam \
--to=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rdreier@cisco.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
Powered by JetHome