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>,
Li Zefan <lizf@cn.fujitsu.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>
Subject: [PATCH 0/2][RFC] [RFC] tracing: separate out buffer from trace_seq
Date: Tue, 08 Dec 2009 14:54:05 -0500 [thread overview]
Message-ID: <20091208195405.653797300@goodmis.org> (raw)
This is an RFC patch set. The trace_seq currently has its buffer
within the structure itself. But this limits its ability and efficiency.
This patch set separates it out, but now it requires the callers
to supply their own buffer. But this helps out the splice code because
it can now write directly into the splice pages.
This may be too much for 33? But it is a nice fix.
Thoughs?
The following patches are in:
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-2.6-trace.git
branch: rfc/tracing/core
Steven Rostedt (2):
tracing: Change trace_seq to use separate buffer
tracing: Write directly into splice page for trace_pipe
----
include/linux/ftrace_event.h | 6 ++++-
include/linux/trace_seq.h | 22 +++++++++++++++-
include/trace/ftrace.h | 20 +++++++++++----
kernel/trace/ftrace.c | 3 +-
kernel/trace/trace.c | 54 ++++++++++++++++-------------------------
kernel/trace/trace_events.c | 45 +++++++++++++++++++++++++++++++----
kernel/trace/trace_ksym.c | 10 +++++++-
kernel/trace/trace_output.c | 24 ++++++++++--------
8 files changed, 125 insertions(+), 59 deletions(-)
next reply other threads:[~2009-12-08 19:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 19:54 Steven Rostedt [this message]
2009-12-08 19:54 ` [PATCH 1/2][RFC] [PATCH 1/2] tracing: Change trace_seq to use separate buffer Steven Rostedt
2009-12-08 19:54 ` [PATCH 2/2][RFC] [PATCH 2/2] tracing: Write directly into splice page for trace_pipe Steven Rostedt
2009-12-09 9:44 ` [PATCH 0/2][RFC] [RFC] tracing: separate out buffer from trace_seq Lai Jiangshan
2009-12-09 16:26 ` 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=20091208195405.653797300@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--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