From: Steven Rostedt <rostedt@goodmis.org>
To: linux-kernel@vger.kernel.org
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [for-next][PATCH 0/2] tracing: Remove bottle neck mutex in splicing from ring buffer
Date: Tue, 23 Dec 2014 11:13:40 -0500 [thread overview]
Message-ID: <20141223161340.297942985@goodmis.org> (raw)
While profiling with trace-cmd, I found that the there was a global
mutex being taken in the per-cpu splice code. This was slowing down
the recording and causing more missed events than necessary.
By adding a ref count to the tracer, and preventing the tracer from
changing when the ref count is non-zero (when a trace file is opened)
we can remove the taking of the trace_types_lock mutex from the
splice page and speed things up a bit.
git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
for-next
Head SHA1: d716ff71dd12bc6328f84a9ec1c3647daf01c827
Steven Rostedt (Red Hat) (2):
tracing: Add ref count to tracer for when they are being read by pipe
tracing: Remove taking of trace_types_lock in pipe files
----
kernel/trace/trace.c | 126 ++++++++++++++++++---------------------------------
kernel/trace/trace.h | 1 +
2 files changed, 44 insertions(+), 83 deletions(-)
next reply other threads:[~2014-12-23 16:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 16:13 Steven Rostedt [this message]
2014-12-23 16:13 ` [for-next][PATCH 1/2] tracing: Add ref count to tracer for when they are being read by pipe Steven Rostedt
2014-12-23 16:13 ` [for-next][PATCH 2/2] tracing: Remove taking of trace_types_lock in pipe files 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=20141223161340.297942985@goodmis.org \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.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
Powered by JetHome