public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lai Jiangshan <laijs@cn.fujitsu.com>
To: Steven Rostedt <rostedt@goodmis.org>,
	linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
	Andrew Morton <akpm@linux-foundation.org>,
	Frederic Weisbecker <fweisbec@gmail.com>
Subject: [PATCH 0/6] tracing: separate out buffer from trace_seq
Date: Tue, 19 Jan 2010 15:33:42 +0800	[thread overview]
Message-ID: <4B556056.2080101@cn.fujitsu.com> (raw)


Quote from Steven:
"""
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.
"""

Lai Jiangshan (4)
      tracing: bug fix, remove partial zeroed out
      tracing: event_id_read() uses simple buffer instead of trace_seq
      tracing: tracing_stats_read() uses simple buffer instead of trace_seq
      tracing: reduce latency and remove percpu trace_seq

Steven Rostedt (2):
      tracing: Change trace_seq to use separate buffer
      tracing: Write directly into splice page for trace_pipe

Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
---
 include/linux/ftrace_event.h |    9 +++-
 include/linux/trace_seq.h    |   22 +++++++++++-
 include/trace/ftrace.h       |   18 +++------
 kernel/trace/ftrace.c        |    3 +
 kernel/trace/trace.c         |   72 +++++++++++----------------------------
 kernel/trace/trace_events.c  |   78 ++++++++++++++++++++-----------------------
 kernel/trace/trace_ksym.c    |   12 +++---
 kernel/trace/trace_output.c  |   25 ++++++-------
 8 files changed, 110 insertions(+), 129 deletions(-)



                 reply	other threads:[~2010-01-19  7:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4B556056.2080101@cn.fujitsu.com \
    --to=laijs@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rostedt@goodmis.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