From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>
Subject: [PATCH 0/3] [GIT PULL] rebase of lockless ring buffer
Date: Wed, 08 Jul 2009 16:13:12 -0400 [thread overview]
Message-ID: <20090708201312.222046866@goodmis.org> (raw)
Ingo,
This is the same as v2 that I posted a while ago. You asked me to resend
after the merge window. It is now after the merge window and I rebased
the work against latest tip/tracing/core. I made no changes that git
could not figure out itself.
Please pull the latest tip/tracing/ring-buffer-3 tree, which can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
tip/tracing/ring-buffer-3
Steven Rostedt (3):
ring-buffer: make the buffer a true circular link list
ring-buffer: make lockless
ring-buffer: add design document
----
Documentation/trace/ring-buffer-design.txt | 955 ++++++++++++++++++++++++++++
include/linux/ring_buffer.h | 1 -
kernel/trace/ring_buffer.c | 935 ++++++++++++++++++++++-----
kernel/trace/trace.c | 3 -
4 files changed, 1725 insertions(+), 169 deletions(-)
--
next reply other threads:[~2009-07-08 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 20:13 Steven Rostedt [this message]
2009-07-08 20:13 ` [PATCH 1/3] ring-buffer: make the buffer a true circular link list Steven Rostedt
2009-07-08 20:13 ` [PATCH 2/3] ring-buffer: make lockless Steven Rostedt
2009-07-08 21:05 ` Mathieu Desnoyers
2009-07-08 21:16 ` Steven Rostedt
2009-07-08 20:13 ` [PATCH 3/3] ring-buffer: add design document Steven Rostedt
2009-07-10 11:31 ` [PATCH 0/3] [GIT PULL] rebase of lockless ring buffer Ingo Molnar
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=20090708201312.222046866@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 \
--cc=tglx@linutronix.de \
/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