[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190902174630.GF19702@krava>
Date: Mon, 2 Sep 2019 19:46:30 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Arnaldo Carvalho de Melo <acme@...nel.org>
Cc: Alexey Budankov <alexey.budankov@...ux.intel.com>,
Jiri Olsa <jolsa@...nel.org>,
lkml <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Namhyung Kim <namhyung@...nel.org>,
Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Michael Petlan <mpetlan@...hat.com>,
Joe Mario <jmario@...hat.com>,
Kan Liang <kan.liang@...ux.intel.com>,
Andi Kleen <ak@...ux.intel.com>
Subject: Re: [PATCH 3/3] perf stat: Add --per-numa agregation support
On Mon, Sep 02, 2019 at 12:43:29PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Mon, Sep 02, 2019 at 06:13:17PM +0300, Alexey Budankov escreveu:
> >
> > 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:
>
> Agreed
ok, will change
jirka
>
> >
> > # 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
>
> --
>
> - Arnaldo
Powered by blists - more mailing lists