From: David Ahern <dsahern@gmail.com>
To: Stephane Eranian <eranian@google.com>
Cc: Pekka Enberg <penberg@cs.helsinki.fi>,
linux-kernel@vger.kernel.org, acme@redhat.com,
peterz@infradead.org, mingo@elte.hu, robert.richter@amd.com,
ak@linux.intel.com
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v5)
Date: Fri, 23 Sep 2011 07:36:39 -0600 [thread overview]
Message-ID: <4E7C8B67.9030708@gmail.com> (raw)
In-Reply-To: <CABPqkBSpqNWJVhRh4bKRK5PGcCdZhzsJzyeQ53Mh4_7fVUm+wg@mail.gmail.com>
On 09/23/2011 03:04 AM, Stephane Eranian wrote:
> On Fri, Sep 23, 2011 at 10:03 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
>> Hi Stephane!
>>
>> On Fri, Sep 23, 2011 at 10:31 AM, Stephane Eranian <eranian@google.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
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?
next prev parent reply other threads:[~2011-09-23 13:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 12:31 [PATCH] perf: make perf.data more self-descriptive (v5) Stephane Eranian
2011-09-22 15:35 ` David Ahern
2011-09-22 15:40 ` Stephane Eranian
2011-09-22 15:48 ` David Ahern
2011-09-22 21:20 ` Andi Kleen
2011-09-22 21:25 ` Stephane Eranian
2011-09-23 3:26 ` Andi Kleen
2011-09-23 6:28 ` Stephane Eranian
2011-09-23 6:40 ` Pekka Enberg
2011-09-23 7:31 ` Stephane Eranian
2011-09-23 8:03 ` Pekka Enberg
2011-09-23 9:04 ` Stephane Eranian
2011-09-23 9:17 ` Pekka Enberg
2011-09-23 13:36 ` David Ahern [this message]
[not found] ` <CABPqkBTuc_jowJx0PqPPhcCuj6B5dqRaQNiZWiyhhHMN+NkLYg@mail.gmail.com>
2011-09-23 14:09 ` David Ahern
2011-09-23 14:22 ` Stephane Eranian
2011-09-23 22:13 ` Valdis.Kletnieks
2011-09-23 10:13 ` Robert Richter
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=4E7C8B67.9030708@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=peterz@infradead.org \
--cc=robert.richter@amd.com \
/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