From: Andi Kleen <andi@firstfloor.org>
To: Nils Smeds <nils.smeds@gmail.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Andi Kleen <andi@firstfloor.org>,
William Cohen <wcohen@redhat.com>, Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
"David S. Miller" <davem@davemloft.net>,
Robert Richter <robert.richter@amd.com>,
Eric Dumazet <dada1@cosmosbay.com>,
Stephane Eranian <eranian@googlemail.com>,
Paul Mackerras <paulus@samba.org>, Peter Anvin <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
perfctr-devel@lists.sourceforge.net,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [Perfctr-devel] [patch] Performance Counters for Linux, v4
Date: Wed, 17 Dec 2008 10:18:45 +0100 [thread overview]
Message-ID: <20081217091845.GC25779@one.firstfloor.org> (raw)
In-Reply-To: <d484eb1f0812162357n7a851f2fncc0abaae9bd293a4@mail.gmail.com>
> To make life easier for developers not interested in exact measuring, but in
> cross-platform development, PAPI has introduced "generic" events. These are
> documented not to be interpretable in a cross-platform manner - and
> typically consist of aggregation of a number of low-level architecture
> specific events. Instead a measure as PERF_COUNT_CACHE_REFERENCES tries to
> create an event set that is a "best effort" for the platform. Typically it
> would try to count read and write events to L1 and L2, but depending on the
The point was that L1 and L2/L3 behave so differently in practice
due to their latency/bandwidth differences (typically L1 is more like a
slower register file while L3 is more like faster DRAM) that it's unclear
that any generic event not defining what it means is any useful.
I could see the point of generic FLC/LLC cache events perhaps,
but not of a single one lumping these two together.
But although with multi core it looks like 3 level hierarchies are
becoming more and more common and also more important to know
about.
-Andi
--
ak@linux.intel.com
next prev parent reply other threads:[~2008-12-17 9:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 21:28 Ingo Molnar
2008-12-15 11:59 ` Paul Mackerras
2008-12-15 12:11 ` Paul Mackerras
2008-12-16 14:22 ` Peter Zijlstra
2008-12-16 23:06 ` Paul Mackerras
2008-12-16 23:51 ` Ingo Molnar
2008-12-17 1:55 ` Andi Kleen
2009-01-16 18:01 ` Corey Ashford
2009-01-16 22:14 ` Maynard Johnson
2009-01-16 23:11 ` Ingo Molnar
2009-01-17 1:26 ` Paul Mackerras
2009-01-17 9:53 ` Andi Kleen
2008-12-17 2:23 ` [Perfctr-devel] " Dan Terpstra
2008-12-17 7:34 ` stephane eranian
2008-12-15 17:44 ` Vince Weaver
2008-12-15 21:07 ` Vince Weaver
2008-12-15 22:13 ` Paul Mackerras
2008-12-15 21:42 ` Paul Mackerras
2008-12-15 22:03 ` stephane eranian
2008-12-16 14:42 ` Peter Zijlstra
2008-12-16 16:55 ` Vince Weaver
2008-12-16 21:52 ` Paul Mackerras
2008-12-16 12:22 ` Pavel Machek
2008-12-16 12:50 ` Ingo Molnar
2008-12-16 12:57 ` Pavel Machek
2008-12-16 13:03 ` Ingo Molnar
2008-12-16 13:13 ` Arjan van de Ven
2008-12-16 20:04 ` Pavel Machek
2008-12-16 14:45 ` Peter Zijlstra
2008-12-16 15:46 ` [Perfctr-devel] " Martin Cracauer
2008-12-16 17:38 ` Vince Weaver
2008-12-16 19:47 ` Corey Ashford
2008-12-16 20:55 ` Vince Weaver
2008-12-16 19:56 ` [Perfctr-devel] " William Cohen
2008-12-17 1:51 ` Andi Kleen
2008-12-17 1:56 ` Samuel Thibault
[not found] ` <d484eb1f0812162357n7a851f2fncc0abaae9bd293a4@mail.gmail.com>
2008-12-17 9:18 ` Andi Kleen [this message]
[not found] ` <d484eb1f0812170611s597e014cl5fb98d6dd81afd49@mail.gmail.com>
2008-12-17 15:06 ` Andi Kleen
2008-12-17 16:00 ` William Cohen
2008-12-17 20:53 ` Corey Ashford
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=20081217091845.GC25779@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=dada1@cosmosbay.com \
--cc=davem@davemloft.net \
--cc=eranian@googlemail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nils.smeds@gmail.com \
--cc=paulus@samba.org \
--cc=perfctr-devel@lists.sourceforge.net \
--cc=robert.richter@amd.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=tglx@linutronix.de \
--cc=wcohen@redhat.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
Powered by JetHome