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] [day] [month] [year] [list]
Date:	Wed, 17 Nov 2010 18:33:02 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	David Sharp <dhsharp@...gle.com>
Cc:	Douglas Santos <douglas.santos@...ymtl.ca>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"ltt-dev@...ts.casi.polymtl.ca" <ltt-dev@...ts.casi.polymtl.ca>,
	Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Michael Rubin <mrubin@...gle.com>
Subject: Re: Benchmarks of kernel tracing options 2 (ftrace, lttng and perf)

On Wed, 2010-11-17 at 15:22 -0800, David Sharp wrote:
> On Wed, Nov 17, 2010 at 2:56 PM, Douglas Santos
> <douglas.santos@...ymtl.ca> wrote:
> > Quoting Steven Rostedt <rostedt@...dmis.org>:
> >> On Wed, 2010-11-17 at 16:31 -0500, Douglas Santos wrote:
> >> > Hi all,
> >> >
> >> > This is a response to a benchmark, submitted a few weeks ago, comparing
> >> kernel
> >> > tracing options.
> >> > http://lkml.org/lkml/2010/10/28/422
> >> >
> >> > We followed the methodology described in the link bellow,
> >> > but using the shellscripts posted there to reproduce autotest scripts.
> >> > http://lkml.org/lkml/2010/10/28/261
> >> >
> >> > We disabled the extra syscall tracing on lttng, for a fair comparison.
> >> > http://lkml.org/lkml/2010/10/28/290
> >> >
> >> > Average results with tracing "on":
> >> >
> >> > lttng:  220 ns
> >> > ftrace: 260 ns
> >>
> >> Heh, so ftrace got worse with the new kernel?
> 
> Steve, can you explain how you're drawing that conclusion? Did Douglas
> run this benchmark before on a previous kernel (I didn't see it if
> so)?

Oops, no, I was thinking that this was from your tests. I remember
asking you to try the new kernel. I think I got you and Douglas
confused :-)

-- Steve


--
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/

Powered by blists - more mailing lists