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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <y0my6yuocth.fsf@ton.toronto.redhat.com>
Date:	Fri, 05 Dec 2008 10:34:50 -0500
From:	fche@...hat.com (Frank Ch. Eigler)
To:	Jiaying Zhang <jiayingz@...gle.com>
Cc:	Steven Rostedt <srostedt@...hat.com>, linux-kernel@...r.kernel.org,
	Michael Rubin <mrubin@...gle.com>,
	Martin Bligh <mbligh@...gle.com>,
	Michael Davidson <md@...gle.com>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC PATCH 3/3] kernel tracing prototype

Jiaying Zhang <jiayingz@...gle.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/