The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Mathieu Desnoyers <compudj@krystal.dyndns.org>
Subject: [PATCH 0/2] [GIT PULL] tracing: performance boosts for recording traces
Date: Wed, 11 Nov 2009 23:41:42 -0500	[thread overview]
Message-ID: <20091112044142.741419929@goodmis.org> (raw)


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(-)

             reply	other threads:[~2009-11-12  4:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-12  4:41 Steven Rostedt [this message]
2009-11-12  4:41 ` [PATCH 1/2] [PATCH 1/2] ring-buffer: Add multiple iterations between benchmark timestamps Steven Rostedt
2009-11-12  4:41 ` [PATCH 2/2] [PATCH 2/2] tracing: do not disable interrupts for trace_clock_local Steven Rostedt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091112044142.741419929@goodmis.org \
    --to=rostedt@goodmis.org \
    --cc=akpm@linux-foundation.org \
    --cc=compudj@krystal.dyndns.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox