All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephane Eranian <eranian@google.com>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: linux-kernel@vger.kernel.org, acme@redhat.com,
	peterz@infradead.org, mingo@elte.hu, dsahern@gmail.com,
	robert.richter@amd.com, ak@linux.intel.com
Subject: Re: [PATCH] perf: make perf.data more self-descriptive (v5)
Date: Fri, 23 Sep 2011 09:31:04 +0200	[thread overview]
Message-ID: <CABPqkBQSBKS+bnLhStzV4PTrE+Qrb1XyeR5FEyn4d+NFZrhuOQ@mail.gmail.com> (raw)
In-Reply-To: <CAOJsxLFDaYxevsH8UYEeZJrz7HCZSg89_XTaXP=hPTTG2HH9=w@mail.gmail.com>

On Fri, Sep 23, 2011 at 8:40 AM, Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Thu, Sep 22, 2011 at 3:31 PM, Stephane Eranian <eranian@google.com> wrote:
>> # CPU0 sibling cores  : 0-3
>> # CPU0 sibling threads: 0
>> # CPU1 sibling cores  : 0-3
>> # CPU1 sibling threads: 1
>> # CPU2 sibling cores  : 0-3
>> # CPU2 sibling threads: 2
>> # CPU3 sibling cores  : 0-3
>> # CPU3 sibling threads: 3
>> # total memory: 8093212 kB
>> # cpuid : GenuineIntel,6,15,11
>
> 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.

  reply	other threads:[~2011-09-23  7:31 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 [this message]
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
     [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=CABPqkBQSBKS+bnLhStzV4PTrE+Qrb1XyeR5FEyn4d+NFZrhuOQ@mail.gmail.com \
    --to=eranian@google.com \
    --cc=acme@redhat.com \
    --cc=ak@linux.intel.com \
    --cc=dsahern@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.