[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160216112814.GA24086@krava.brq.redhat.com>
Date: Tue, 16 Feb 2016 12:28:14 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: Ingo Molnar <mingo@...nel.org>
Cc: Jiri Olsa <jolsa@...nel.org>,
Arnaldo Carvalho de Melo <acme@...nel.org>,
lkml <linux-kernel@...r.kernel.org>,
David Ahern <dsahern@...il.com>,
Namhyung Kim <namhyung@...nel.org>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: Re: [PATCH 0/5] perf tools: Store CPU cache details under perf data
On Tue, Feb 16, 2016 at 09:14:13AM +0100, Ingo Molnar wrote:
>
> * Jiri Olsa <jolsa@...nel.org> wrote:
>
> > hi,
> > adding support to store CPU cache details under perf data.
> >
> > $ perf report --header-only -I
> > ...
> > # cache info:
> > # L1 Data 32K [0-1]
> > # L1 Instruction 32K [0-1]
> > # L1 Data 32K [2-3]
> > # L1 Instruction 32K [2-3]
> > # L2 Unified 256K [0-1]
> > # L2 Unified 256K [2-3]
> > # L3 Unified 4096K [0-3]
>
> Very small UI nit, wouldn't it be nicer if this displayed tabular output, and if
> numbers were adjusted to their decimal point, i.e. something like:
>
> > # CPU cache info:
> > # L1 Data 32K [0-1]
> > # L1 Instruction 32K [0-1]
> > # L1 Data 32K [2-3]
> > # L1 Instruction 32K [2-3]
> > # L2 Unified 256K [0-1]
> > # L2 Unified 256K [2-3]
> > # L3 Unified 4096K [0-3]
>
> (Also note that it says 'CPU cache info' - there are a lot of caches in the
> system.)
yep, looks better.. will change
thanks,
jirka
Powered by blists - more mailing lists