From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/5] [GIT PULL] ring-buffer: Various optimizations
Date: Tue, 19 Oct 2010 13:54:32 -0400 [thread overview]
Message-ID: <20101019175432.854431527@goodmis.org> (raw)
Ingo,
I based this tree off of Linus's latest, since it removes the macro
that was updated in rc8. This patch set supplies a better fix,
albeit, a bit more complex of a change, hence not going into the rc.
Please pull the latest tip/perf/ringbuffer tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/perf/ringbuffer
Steven Rostedt (5):
ring-buffer: Make write slow path out of line
ring-buffer: Bind time extend and data events together
ring-buffer: Remove condition to add timestamp in fast path
ring-buffer: Micro-optimize with some strategic inlining
ring-buffer: Remove unused macro RB_TIMESTAMPS_PER_PAGE
----
include/linux/ring_buffer.h | 12 --
kernel/trace/ring_buffer.c | 344 ++++++++++++++++++++++--------------------
2 files changed, 180 insertions(+), 176 deletions(-)
next reply other threads:[~2010-10-19 19:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-19 17:54 Steven Rostedt [this message]
2010-10-19 17:54 ` [PATCH 1/5] ring-buffer: Make write slow path out of line Steven Rostedt
2010-10-19 17:54 ` [PATCH 2/5] ring-buffer: Bind time extend and data events together Steven Rostedt
2010-10-19 20:46 ` Thomas Gleixner
2010-10-20 13:06 ` Steven Rostedt
2010-10-19 17:54 ` [PATCH 3/5] ring-buffer: Remove condition to add timestamp in fast path Steven Rostedt
2010-10-19 17:54 ` [PATCH 4/5] ring-buffer: Micro-optimize with some strategic inlining Steven Rostedt
2010-10-19 17:54 ` [PATCH 5/5] ring-buffer: Remove unused macro RB_TIMESTAMPS_PER_PAGE 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=20101019175432.854431527@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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