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-next>] [day] [month] [year] [list]
Date:	Wed, 11 Nov 2009 23:41:42 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	linux-kernel@...r.kernel.org
Cc:	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Mathieu Desnoyers <compudj@...stal.dyndns.org>
Subject: [PATCH 0/2] [GIT PULL] tracing: performance boosts for recording traces


Ingo,

The first patch is really a fix to the ring_buffer_benchmark. It was
not giving a correct representation of the time of a trace. The
logic to time the trace was 1/3 of the measurement.

The second patch removes the disabling of interrupts in trace_clock_local.
This showed a 30 to 40 ns latency.

I'm still seeing the time stamp being a large overhead in the tracing.
I'll be posting an RFC patch set on using normalizing the timestamp
on read, to take some of the work out of the write side. This
drops the write from 179 ns to 151 ns. More about that later.

Please pull the latest tip/tracing/core tree, which can be found at:

  git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/core


Steven Rostedt (2):
      ring-buffer: Add multiple iterations between benchmark timestamps
      tracing: do not disable interrupts for trace_clock_local

----
 kernel/trace/ring_buffer_benchmark.c |   25 ++++++++++++++++---------
 kernel/trace/trace_clock.c           |    8 +++++---
 2 files changed, 21 insertions(+), 12 deletions(-)
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ