From: Ingo Molnar <mingo@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
mingo@elte.hu, ak@linux.intel.com, acme@redhat.com,
jolsa@redhat.com, namhyung.kim@lge.com
Subject: Re: [PATCH 0/2] perf: add new uncore command
Date: Thu, 31 Jan 2013 15:21:02 +0100 [thread overview]
Message-ID: <20130131142102.GA7339@gmail.com> (raw)
In-Reply-To: <1359640479-5289-1-git-send-email-eranian@google.com>
* Stephane Eranian <eranian@google.com> wrote:
> This patchset adds a new command to perf: perf uncore.
> It is used to measure processor socket-level metrics
> on a system-wide basis and at all priv levels.
>
> The command comes with a set of predefined key metrics
> which are useful to measure multi-socket system imbalance
> and various bandwidths.
>
> The following metrics are currently defined:
> - memory bandwidth (Nehalem, Westmere, SandyBridge-EP)
> - PCIe bandwidth (SandyBridge-EP)
> - QPI bandwidth (SandyBridge-EP)
> - C-state residency (SandyBridge-EP)
>
> Others can be added in the future.
>
> The command provides options to modify the unit of the metrics
> (default: MB/s for bandwidth).
>
> Example on Nehalem:
>
> # perf uncore
> #------------------------------
> # Socket0 |
> #------------------------------
> # RAM Bandwidth |
> # Wr Rd|
> # MB/s MB/s|
> #------------------------------
> 4954.99 14897.29
> 4953.97 14894.56
> 4947.52 14874.97
>
> To make plotting easier, the output can be augmented with a timestamp:
>
> # perf uncore -T
> #----------------------------------------
> # | Socket0 |
> # |------------------------------
> # Time | RAM Bandwidth |
> # in | Wr Rd|
> # secs | MB/s MB/s|
> #----------------------------------------
> 1 4952.50 14890.49
> 2 4955.55 14900.19
> 3 4949.13 14879.60
> 4 4954.66 14896.26
Looks really useful - how about naming it in a bit more generic
way, because I'm quite sure this command will become popular and
'perf uncore' is a bit un-intutive.
A couple of possibilities:
perf system
perf hw
perf hw-stat
and also adding subcommands instead of options for the various
views/metrics, such as:
perf hw ram
perf hw pci
perf hw qpi
perf hw cstate
etc.
A plain 'perf hw' command would then list the available
sub-commands and inform the user about the (current) set of
hw subsystems that provide metrics.
Hm?
Thanks,
Ingo
next prev parent reply other threads:[~2013-01-31 14:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 13:54 [PATCH 0/2] perf: add new uncore command Stephane Eranian
2013-01-31 13:54 ` [PATCH 1/2] perf tools: add cpu_map__get_socket() Stephane Eranian
2013-01-31 13:54 ` [PATCH 2/2] perf: add new perf uncore command Stephane Eranian
2013-02-01 8:45 ` Namhyung Kim
2013-01-31 14:21 ` Ingo Molnar [this message]
2013-01-31 14:32 ` [PATCH 0/2] perf: add new " Stephane Eranian
2013-02-01 8:42 ` Namhyung Kim
2013-02-02 1:35 ` Andi Kleen
2013-02-04 13:33 ` Jiri Olsa
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=20130131142102.GA7339@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=namhyung.kim@lge.com \
--cc=peterz@infradead.org \
/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