[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABPqkBSpqNWJVhRh4bKRK5PGcCdZhzsJzyeQ53Mh4_7fVUm+wg@mail.gmail.com>
Date: Fri, 23 Sep 2011 11:04:05 +0200
From: Stephane Eranian <eranian@...gle.com>
To: Pekka Enberg <penberg@...helsinki.fi>
Cc: linux-kernel@...r.kernel.org, acme@...hat.com,
peterz@...radead.org, mingo@...e.hu, dsahern@...il.com,
robert.richter@....com, ak@...ux.intel.com
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v5)
On Fri, Sep 23, 2011 at 10:03 AM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> Hi Stephane!
>
> On Fri, Sep 23, 2011 at 10:31 AM, Stephane Eranian <eranian@...gle.com> wrote:
>>> So how important is this information? The output is going to be somewhat
>>> awkward for very large CPU counts... :-)
>>>
>> It is useful to determine how CPUs share caches for instance.
>> It can get large but large, but the meta-data header is not printed by
>> default, you need to request it with the -I option.
>
> Well, sure but it blocks rest of the interesting information too. It seems to me
> that the CPU information could be truncated to some sane limit by default and
> introduce a command line option for users that really want to see all of it.
>
Ok, so here is a proposal:
- reorder the info so one liners appear first
- display the "truncated" info by default (no option)
- truncated: numa topo, cpu topo, stop after 4 cpus/nodes, print msg
to hint at -I option
- use -I to print the extended header info report
That way we do no introduce two options just for the header information.
How about that instead?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists