|| ||David Miller <davem-AT-davemloft.net>|
|| ||Re: [patch 0/3] [Announcement] Performance Counters for Linux|
|| ||Mon, 08 Dec 2008 03:58:28 -0800 (PST)|
|| ||eranian-AT-gmail.com, paulus-AT-samba.org, a.p.zijlstra-AT-chello.nl,
dada1-AT-cosmosbay.com, robert.richter-AT-amd.com, arjan-AT-infradead.org,
|| ||Article, Thread
From: Ingo Molnar <email@example.com>
Date: Mon, 8 Dec 2008 12:11:53 +0100
> We did what we believe to be the right thing: we gave performance
> counters the proper high-level abstraction they _deserve_, and we made
> performance counters a prime-time Linux citizen as well.
Seperate counters that are read independently is fundamentally wrong,
no matter how many times you try to say it isn't. In fact it has
been shown (repeatedly) that this abstraction is at the wrong level.
People want to correlate, and it's not possible to do that if the
counters are sampled seperately.
We also don't want half-megabyte PMU tables in the kernel, nor the
complex logic about how PMU counter X can configured when counter Y is
configured for event A. All of that belongs in userspace.
We also want to support PMUs that do not generate an overflow
Really, all of the backlash these new patches have received is not
about how clean the abstraction is, but rather whether it can even
do the job properly.
And also, another part of the backlash is that the poor perfmon3
person was completely blindsided by this new stuff. Which to be
honest was pretty unfair. He might have had great ideas about
the requirements (even if you don't give a crap about his approach
to achieving those requirements) and thus could have helped avoid
the past few days of churn.
to post comments)