Re: [patch] Performance Counters for Linux, v3
From: Ingo Molnar
Date: Fri Dec 12 2008 - 01:22:45 EST
* Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote:
> On Thu, 11 Dec 2008 16:52:30 +0100
> Ingo Molnar <mingo@xxxxxxx> wrote:
>
> > To: linux-kernel@xxxxxxxxxxxxxxx
> > Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Stephane Eranian <eranian@xxxxxxxxxxxxxx>, Eric Dumazet <dada1@xxxxxxxxxxxxx>, Robert Richter <robert.richter@xxxxxxx>, Arjan van de Veen <arjan@xxxxxxxxxxxxx>, Peter Anvin <hpa@xxxxxxxxx>, Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>, Paul Mackerras <paulus@xxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>
>
> Please copy perfctr-devel@xxxxxxxxxxxxxxxxxxxxx on all this. That is
> where the real-world people who use these facilities on a regular basis
> hang out.
Sure, we'll do that for v4.
The reason we kept posting this to lkml initially was because there is a
visible detachment of this community from kernel developers. And that is
at least in part because this stuff has never been made interesting
enough to kernel developers. I dont remember a _single_ perfmon-generated
profile (be that user-space or kernel-space) in my mailbox before - and
optimizing the kernel is supposed to be one of the most important aspects
of performance tuning.
That's why we concentrate on making this useful and interesting to kernel
developers too via KernelTop, that's why we made the BTS/[PEBS] hardware
tracer available via an ftrace plugin, etc.
Furthermore, kernel developers tend to be quite good at co-designing,
influencing [and flaming ;-) ] such APIs at the early prototype stages,
so the main early technical feedback we were looking for on the kernel
side structure was lkml. But the wider community is not ignored either,
of course - with v4 it might be useful already for wider circulation.
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/