Re: Experiences with kprobes

[Roland McGrath <roland at redhat dot com>]

For finding hot spots with low overhead, oprofile may be the better tool
for what you need.  That said, we are certainly aware of kprobes
performance being an issue and I suspect it will get somewhat better as the
project develops.  Something we have been looking for is specific
quantitative definitions of what "fast enough" is for various applications.
If you have some estimate of the overhead you are seeing, the frequency of
hits in your load scenario, and the (lower) range of overhead that would
make probing techniques useful to you that are prohibitive at the moment,
this would be good information to feed into our performance goals.


Thanks,
Roland