From: Alexey Budankov <alexey.budankov@linux.intel.com>
To: Jiri Olsa <jolsa@kernel.org>, Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Michael Petlan <mpetlan@redhat.com>,
Joe Mario <jmario@redhat.com>,
Kan Liang <kan.liang@linux.intel.com>,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 3/3] perf stat: Add --per-numa agregation support
Date: Mon, 2 Sep 2019 18:13:17 +0300 [thread overview]
Message-ID: <bdf81661-4c70-797f-51f2-726f4458d812@linux.intel.com> (raw)
In-Reply-To: <20190902121255.536-4-jolsa@kernel.org>
On 02.09.2019 15:12, Jiri Olsa wrote:
> Adding new --per-numa option to aggregate counts per NUMA
> nodes for system-wide mode measurements.
>
> You can specify --per-numa in live mode:
>
> # perf stat -a -I 1000 -e cycles --per-numa
> # time numa cpus counts unit events
It might probably better have 'node' instead of 'numa' as in the
option name '--per-node' as in the table header, like this:
# time node cpus counts unit events
1.000542550 0 20 6,202,097 cycles
1.000542550 1 20 639,559 cycles
2.002040063 0 20 7,412,495 cycles
2.002040063 1 20 2,185,577 cycles
3.003451699 0 20 6,508,917 cycles
3.003451699 1 20 765,607 cycles
...
BR,
Alexey
next prev parent reply other threads:[~2019-09-02 15:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 12:12 [PATCH 0/3] perf stat: Add --per-numa option Jiri Olsa
2019-09-02 12:12 ` [PATCH 1/3] libperf: Add perf_cpu_map__max function Jiri Olsa
2019-09-02 13:57 ` Arnaldo Carvalho de Melo
2019-09-20 16:21 ` [tip: perf/urgent] libperf: Adopt perf_cpu_map__max() function tip-bot2 for Jiri Olsa
2019-09-02 12:12 ` [PATCH 2/3] perf tools: Add perf_env__numa_node function Jiri Olsa
2019-09-02 13:57 ` Arnaldo Carvalho de Melo
2019-09-02 14:16 ` Jiri Olsa
2019-09-02 12:12 ` [PATCH 3/3] perf stat: Add --per-numa agregation support Jiri Olsa
2019-09-02 15:13 ` Alexey Budankov [this message]
2019-09-02 15:43 ` Arnaldo Carvalho de Melo
2019-09-02 17:46 ` 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=bdf81661-4c70-797f-51f2-726f4458d812@linux.intel.com \
--to=alexey.budankov@linux.intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=jmario@redhat.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpetlan@redhat.com \
--cc=namhyung@kernel.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
all inboxes | Powered by JetHome®