Re: [PATCH] perf: make perf.data more self-descriptive (v5)

[David Ahern]

On 09/23/2011 03:04 AM, Stephane Eranian wrote:
> On Fri, Sep 23, 2011 at 10:03 AM, Pekka Enberg <penberg@xxxxxxxxxxxxxx> wrote:
>> Hi Stephane!
>>
>> On Fri, Sep 23, 2011 at 10:31 AM, Stephane Eranian <eranian@xxxxxxxxxx> 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

Earlier I gave an example for a 2 socket, quad-core with hyperthreading
(16 cpus total):
    https://lkml.org/lkml/2011/9/6/355
The information is repetitive. It would be better to devise a way to
reduce the repetition versus truncate the information.

David


> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/