All of lore.kernel.org
 help / color / mirror / Atom feed
From: Valdis.Kletnieks@vt.edu
To: Stephane Eranian <eranian@google.com>
Cc: "Arnaldo Carvalho de Melo" <acme@infradead.org>,
	"Ingo Molnar" <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	"David S. Miller" <davem@davemloft.net>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>,
	"Mike Galbraith" <efault@gmx.de>,
	"Paul Mackerras" <paulus@samba.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Tom Zanussi" <tzanussi@gmail.com>,
	"Arnaldo Carvalho de Melo" <acme@redhat.com>
Subject: Re: [PATCH 1/5] perf stat: add perf stat -B to pretty print large numbers
Date: Mon, 31 May 2010 16:49:02 -0400	[thread overview]
Message-ID: <77282.1275338942@localhost> (raw)
In-Reply-To: Your message of "Mon, 31 May 2010 21:30:36 +0200." <AANLkTimBxG-2TVC7hAfvRHWupa8T7FaVEcDTnAMCtQWy@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2794 bytes --]

On Mon, 31 May 2010 21:30:36 +0200, Stephane Eranian said:
> >> instance LC_NUMERIC=en_US.UTF8. You need to pass -B to activate this
>>> feature. This way existing scripts parsing the output do not need to be
>>> changed. Here is an example.

Two examples, actually...

>>>
>>> $ perf stat noploop 2
>>> noploop for 2 seconds
>>>
>>>  Performance counter stats for 'noploop 2':
>>>
>>>         1998.347031  task-clock-msecs         #      0.998 CPUs
>>>                  61  context-switches         #      0.000 M/sec
>>>                   0  CPU-migrations           #      0.000 M/sec
>>>                 118  page-faults              #      0.000 M/sec
>>>       4,138,410,900  cycles                   #   2070.917 M/sec  (scaled from 70.01%)
>>>       2,062,650,268  instructions             #      0.498 IPC    (scaled from 70.01%)
>>>       2,057,653,466  branches                 #   1029.678 M/sec  (scaled from 70.01%)
>>>              40,267  branch-misses            #      0.002 %      (scaled from 30.04%)
>>>       2,055,961,348  cache-references         #   1028.831 M/sec  (scaled from 30.03%)
>>>              53,725  cache-misses             #      0.027 M/sec  (scaled from 30.02%)
>>>
>>>         2.001393933  seconds time elapsed
>>>
>>> $ perf stat -B  noploop 2
>>> noploop for 2 seconds
>>>
>>>  Performance counter stats for 'noploop 2':
>>>
>>>         1998.297883  task-clock-msecs         #      0.998 CPUs
>>>                  59  context-switches         #      0.000 M/sec
>>>                   0  CPU-migrations           #      0.000 M/sec
>>>                 119  page-faults              #      0.000 M/sec
>>>       4,131,380,160  cycles                   #   2067.450 M/sec  (scaled from 70.01%)
>>>       2,059,096,507  instructions             #      0.498 IPC    (scaled from 70.01%)
>>>       2,054,681,303  branches                 #   1028.216 M/sec  (scaled from 70.01%)
>>>              25,650  branch-misses            #      0.001 %      (scaled from 30.05%)
>>>       2,056,283,014  cache-references         #   1029.017 M/sec  (scaled from 30.03%)
>>>              47,097  cache-misses             #      0.024 M/sec  (scaled from 30.02%)
>>>
>>>         2.001391016  seconds time elapsed
>>
>> Is it me, or did -B not make any difference for these two examples?
>> I'm confused.

> Did you set the LC_NUMERIC environement variable?

I meant I was reading the two examples given, and I'm seeing commas in
the same places, -B or not -B.  I was sort of expecting that the first
example wouldn't have commas in it, or something?  Or were those two
examples *supposed* to be identical, and there's a not-shown 3rd example
that shows what you get if you use -B and set the LC_NUMERIC variable?

[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2010-05-31 20:52 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19  2:08 [GIT PULL v2 0/5] perf tools fixes and improvements Arnaldo Carvalho de Melo
2010-05-19  2:08 ` [PATCH 1/5] perf stat: add perf stat -B to pretty print large numbers Arnaldo Carvalho de Melo
2010-05-19  6:28   ` Ingo Molnar
2010-05-31 19:11   ` Valdis.Kletnieks
2010-05-31 19:30     ` Stephane Eranian
2010-05-31 20:49       ` Valdis.Kletnieks [this message]
2010-05-31 23:11         ` Arnaldo Carvalho de Melo
2010-05-31 23:37           ` Arnaldo Carvalho de Melo
2010-05-19  2:08 ` [PATCH 2/5] perf tools: Remove some unused functions Arnaldo Carvalho de Melo
2010-05-19  2:08 ` [PATCH v2 3/5] perf probe: Fix some error exit paths Arnaldo Carvalho de Melo
2010-05-19  2:08 ` [PATCH v2 4/5] perf probe: Don't call die() Arnaldo Carvalho de Melo
2010-05-19  2:08 ` [PATCH 5/5] perf tools: remove xstrndup, xmalloc, xzalloc Arnaldo Carvalho de Melo
  -- strict thread matches above, loose matches on Subject: below --
2010-05-19  0:27 [GIT PULL 0/5] perf tools fixes and improvements Arnaldo Carvalho de Melo
2010-05-19  0:27 ` [PATCH 1/5] perf stat: add perf stat -B to pretty print large numbers Arnaldo Carvalho de Melo

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=77282.1275338942@localhost \
    --to=valdis.kletnieks@vt.edu \
    --cc=acme@infradead.org \
    --cc=acme@redhat.com \
    --cc=davem@davemloft.net \
    --cc=efault@gmx.de \
    --cc=eranian@google.com \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --cc=peterz@infradead.org \
    --cc=tzanussi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.