[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.0.9999.0711142006020.7260@twinlark.arctic.org>
Date: Wed, 14 Nov 2007 20:20:22 -0800 (PST)
From: dean gaudet <dean@...tic.org>
To: Andi Kleen <andi@...stfloor.org>
cc: Christoph Hellwig <hch@...radead.org>,
Paul Mackerras <paulus@...ba.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg KH <gregkh@...e.de>, Philip Mucci <mucci@...utk.edu>,
eranian@....hp.com, William Cohen <wcohen@...hat.com>,
Robert Richter <robert.richter@....com>,
linux-kernel@...r.kernel.org, Perfmon <perfmon@...ali.hpl.hp.com>,
perfmon2-devel@...ts.sourceforge.net,
OSPAT devel <ospat-devel@...utk.edu>,
papi list <ptools-perfapi@...utk.edu>
Subject: Re: [perfmon] Re: [perfmon2] perfmon2 merge news
On Wed, 14 Nov 2007, Andi Kleen wrote:
> Later a syscall might be needed with event multiplexing, but that seems
> more like a far away non essential feature.
actually multiplexing is the main feature i am in need of. there are an
insufficient number of counters (even on k8 with 4 counters) to do
complete stall accounting or to get a general overview of L1d/L1i/L2 cache
hit rates, average miss latency, time spent in various stalls, and the
memory system utilization (or HT bus utilization). this runs out to
something like 30 events which are interesting... and re-running a
benchmark over and over just to get around the lack of multiplexing is a
royal pain in the ass.
it's not a "far away non-essential feature" to me. it's something i would
use daily if i had all the pieces together now (and i'm constrained
because i cannot add an out-of-tree patch which adds unofficial syscalls
to the kernel i use).
-dean
-
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