From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
prasad@linux.vnet.ibm.com,
Linus Torvalds <torvalds@linux-foundation.org>,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
David Wilder <dwilder@us.ibm.com>,
hch@lst.de, Martin Bligh <mbligh@google.com>,
Christoph Hellwig <hch@infradead.org>
Subject: [RFC PATCH 0/2 v2] Unified trace buffer (take two)
Date: Thu, 25 Sep 2008 11:58:07 -0400 [thread overview]
Message-ID: <20080925155807.158539649@goodmis.org> (raw)
Again: this is a proof of concept, just spitting out code for comments.
Here's my second attempt.
Changes since version 1:
- Ripped away all the debugfs and event registration from ring buffers.
- Removed the mergesort from the ringbuffer and pushed that up to the
tracer.
- Changed the event header to what Linus suggested (we can discuss this
and try other suggestions for v3, namely Peter Zijlstras ideas).
struct {
u32 time_delta:27, type:5;
u32 data;
u64 array[];
};
- Added timestamp at beginning of each page and implemented a way
for all events to get the full timestamp from the previous.
- The changes to ftrace on this release was much less than the first
one.
Comments?
-- Steve
next reply other threads:[~2008-09-25 16:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 15:58 Steven Rostedt [this message]
2008-09-25 15:58 ` [RFC PATCH 1/2 v2] Unified trace buffer Steven Rostedt
2008-09-25 17:02 ` Linus Torvalds
2008-09-25 17:16 ` Steven Rostedt
2008-09-25 17:25 ` Linus Torvalds
2008-09-25 17:46 ` Steven Rostedt
2008-09-25 17:35 ` Mathieu Desnoyers
2008-09-25 17:48 ` Steven Rostedt
2008-09-25 18:25 ` Mathieu Desnoyers
2008-09-25 15:58 ` [RFC PATCH 2/2 v2] ftrace: make work with new ring buffer 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=20080925155807.158539649@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=dwilder@us.ibm.com \
--cc=fche@redhat.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.