![]() | |||||||||||||
Messages in this thread |
Mathieu Desnoyers wrote: > And about those extra cycles.. according to : > Documentation/kprobes.txt > "6. Probe Overhead > > On a typical CPU in use in 2005, a kprobe hit takes 0.5 to 1.0 > microseconds to process. Specifically, a benchmark that hits the same > probepoint repeatedly, firing a simple handler each time, reports 1-2 > million hits per second, depending on the architecture. A jprobe or > return-probe hit typically takes 50-75% longer than a kprobe hit. > When you have a return probe set on a function, adding a kprobe at > the entry to that function adds essentially no overhead. [snip] > So, 1 microsecond seems more like 1500-2000 cycles to me, not 50. So call it 2000 cycles, now go measure it in *real* life benchmarks and not some artificial I call this one syscall that hits the probe every time in a tight loop, kinda thing. Show us some *real* numbers please. Jes - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-09-18 10:19 [from the cache] ©2003-2008 | |||||||||||||