[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABPqkBQSBKS+bnLhStzV4PTrE+Qrb1XyeR5FEyn4d+NFZrhuOQ@mail.gmail.com>
Date: Fri, 23 Sep 2011 09:31:04 +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 8:40 AM, Pekka Enberg <penberg@...helsinki.fi> wrote:
> On Thu, Sep 22, 2011 at 3:31 PM, Stephane Eranian <eranian@...gle.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.
--
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