PEBS is important in our NUMAtop design to measure memory access
latency for application. We will enhance kcpc to support PEBS and
uncore events. If we can talk with CPC engineers and get their help,
it will be great.
Yes, I think that's essential. I'll put you guys in contact
with each other.
I'm sure sampling is probably what you need to get the job done
properly. However, don't forget about the DTrace cpc provider
as it may well be of use to you here.
We have considered CPC provider in our design to help user locate what
function caused most of remote memory access, but this feature will
not be in current implementation. Both NUMAtop and CPC provider need
access performance counters, they can not program performance counter
simultaneously. When customer identifys that his application may be
impacted by remote memory access through NUMAtop. If he want to know
the top functions which leads to remote memory access, NUMAtop can
enter into CPC provider mode for sampling and provides such
information.
OK. If we could implement a sampling framework it would be a
natural and highly useful extension to provide a sampling
provider for DTrace. We've spoken about that internally but I'm
not 100% sure what it would look like at the minute. All food
for thought though.
Jon.
_______________________________________________
perf-discuss mailing list
perf-discuss@opensolaris.org
