Re: [RFC PATCH 3/3] kernel tracing prototype

[Frank Ch. Eigler]

Jiaying Zhang <jiayingz@xxxxxxxxxx> writes:

> To better answer the question why we want to implement a new kernel
> tracing prototype, here are some performance results we collected before
> with the tbench benchmark. 

Thanks.

> - vanilla 2.6.26 kernel, CONFIG_MARKERS=n
> Throughput 759.352 MB/sec 4
> - markers compiled in, tracing disabled
> Throughput 754.18 MB/sec 4

Is your kernel built with -freorder-blocks?  This option dramatically
reduces the cost of inactive markers/tracepoints.

> - tracing syscall entry/exit, use markers, not logging data to ring_buffer
> Throughput 715.68 MB/sec 4
> - tracing syscall entry/exit, use markers, logging data to ring_buffer
> Throughput 654.056 MB/sec 4

(By the way, how are you doing syscall entry/exit tracing?)


- FChE
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/