If the kernel was configured with Klogger's internal benchmarking mechanism (kernel option [Kernel hacking --> KLogger benchmarks] enabled), you will find a directory called /proc/sys/klogger/benchmarks, in which there is a file matching each event's name. The file's contents is the event's logging overhead, in CPU cycles.
When a file is read, the matching event is logged several times to measure the average overhead. The number of iterations can be tuned using the special /proc/sys/klogger/benchmarks/iterations file (default is 1000 iterations).
For example, on our PentiumIV machine clocked at 2.8GHz the overhead of the KLOGGER_START event is 234 cycles (83.6 nanoseconds!), while the overhead of the more complex PROCESS_EXISTS (which contain character strings) is 16614 cycles (5.93us).
<433>>