From: Steven Rostedt <rostedt@goodmis.org>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Masami Hiramatsu <mhiramat@kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Yordan Karadzhov <y.karadz@gmail.com>,
Tzvetomir Stoyanov <tz.stoyanov@gmail.com>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
Tom Zanussi <zanussi@kernel.org>,
Jason Behmer <jbehmer@google.com>,
Julia Lawall <julia.lawall@inria.fr>,
Clark Williams <williams@redhat.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Daniel Wagner <wagi@monom.org>, Darren Hart <dvhart@vmware.com>,
Jonathan Corbet <corbet@lwn.net>,
"Suresh E. Warrier" <warrier@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH] ring-buffer: Have nested events still record running time stamp
Date: Thu, 25 Jun 2020 14:09:03 -0400 [thread overview]
Message-ID: <20200625140903.2a1d3e6e@oasis.local.home> (raw)
In-Reply-To: <20200625094454.732790f7@oasis.local.home>
After running my ring buffer benchmark on this update, it went from
55ns to 85ns per event. A 30ns increase! At first I freaked out, but
then noticed that I unnecessarily take the time stamp counter twice,
which is the most expensive operation.
Here's a diff to my patch (I'll send a v2 later) that removes the
double taking of the time stamp.
It also removes the double testing of the absolute value. Which I have
another patch that consolidates that with the info add_timestamp field.
But that patch wont be folded into this.
-- Steve
diff --git a/kernel/trace/ring_buffer.c b/kernel/trace/ring_buffer.c
index a5c3f1608de8..7370c483c6cd 100644
--- a/kernel/trace/ring_buffer.c
+++ b/kernel/trace/ring_buffer.c
@@ -2908,6 +2908,7 @@ __rb_reserve_next(struct ring_buffer_per_cpu *cpu_buffer,
struct buffer_page *tail_page;
unsigned long tail, write, w, next;
u64 delta, before, after;
+ bool abs = false;
/* Don't let the compiler play games with cpu_buffer->tail_page */
tail_page = info->tail_page = READ_ONCE(cpu_buffer->tail_page);
@@ -2916,6 +2917,19 @@ __rb_reserve_next(struct ring_buffer_per_cpu *cpu_buffer,
barrier();
before = READ_ONCE(cpu_buffer->before_stamp);
after = local64_read(&cpu_buffer->write_stamp);
+ barrier();
+ info->ts = rb_time_stamp(cpu_buffer->buffer);
+
+ if (ring_buffer_time_stamp_abs(cpu_buffer->buffer)) {
+ info->delta = info->ts;
+ abs = true;
+ } else {
+ info->delta = info->ts - after;
+ }
+
+ if (unlikely(test_time_stamp(info->delta)))
+ rb_handle_timestamp(cpu_buffer, info);
+
/*
* If preempting an event time update, we may need absolute timestamp.
* Don't bother if this is the start of a new page (w == 0).
@@ -2933,7 +2947,6 @@ __rb_reserve_next(struct ring_buffer_per_cpu *cpu_buffer,
next = READ_ONCE(cpu_buffer->next_write);
WRITE_ONCE(cpu_buffer->next_write, w + info->length);
- info->ts = rb_time_stamp(cpu_buffer->buffer);
/*B*/ WRITE_ONCE(cpu_buffer->before_stamp, info->ts);
/*C*/ write = local_add_return(info->length, &tail_page->write);
@@ -3021,8 +3034,7 @@ __rb_reserve_next(struct ring_buffer_per_cpu *cpu_buffer,
* If this is the first commit on the page, then it has the same
* timestamp as the page itself.
*/
- if (unlikely(!tail && info->add_timestamp != RB_ADD_STAMP_FORCE &&
- !ring_buffer_time_stamp_abs(cpu_buffer->buffer)))
+ if (unlikely(!tail && info->add_timestamp != RB_ADD_STAMP_FORCE && !abs))
info->delta = 0;
/* We reserved something on the buffer */
@@ -3056,7 +3068,6 @@ rb_reserve_next_event(struct trace_buffer *buffer,
struct ring_buffer_event *event;
struct rb_event_info info;
int nr_loops = 0;
- u64 write_stamp;
rb_start_commit(cpu_buffer);
/* The commit page can not change after this */
@@ -3093,18 +3104,6 @@ rb_reserve_next_event(struct trace_buffer *buffer,
if (RB_WARN_ON(cpu_buffer, ++nr_loops > 1000))
goto out_fail;
- write_stamp = local64_read(&cpu_buffer->write_stamp);
- info.ts = rb_time_stamp(cpu_buffer->buffer);
-
- if (ring_buffer_time_stamp_abs(buffer)) {
- info.delta = info.ts;
- rb_handle_timestamp(cpu_buffer, &info);
- } else {
- info.delta = info.ts - write_stamp ;
- if (unlikely(test_time_stamp(info.delta)))
- rb_handle_timestamp(cpu_buffer, &info);
- }
-
event = __rb_reserve_next(cpu_buffer, &info);
if (unlikely(PTR_ERR(event) == -EAGAIN)) {
prev parent reply other threads:[~2020-06-25 18:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:44 Steven Rostedt
2020-06-25 13:53 ` Mathieu Desnoyers
2020-06-25 14:37 ` Steven Rostedt
2020-06-25 16:42 ` Korben Rusek
2020-06-25 18:12 ` Steven Rostedt
2020-06-25 17:55 ` Mathieu Desnoyers
2020-06-25 18:35 ` Steven Rostedt
2020-06-25 19:35 ` Mathieu Desnoyers
2020-06-25 19:58 ` Steven Rostedt
2020-06-26 2:36 ` Steven Rostedt
2020-06-26 3:35 ` Steven Rostedt
2020-06-26 13:58 ` Steven Rostedt
2020-06-26 18:13 ` Mathieu Desnoyers
2020-06-26 18:58 ` Steven Rostedt
2020-06-26 19:39 ` Steven Rostedt
2020-06-30 0:21 ` Steven Rostedt
2020-06-30 3:13 ` Mathieu Desnoyers
2020-06-30 3:26 ` Steven Rostedt
2020-06-25 19:04 ` Steven Rostedt
2020-06-25 19:58 ` Mathieu Desnoyers
2020-06-25 20:42 ` Steven Rostedt
2020-06-25 19:09 ` Steven Rostedt
2020-06-25 20:03 ` Mathieu Desnoyers
2020-06-25 18:09 ` Steven Rostedt [this message]
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=20200625140903.2a1d3e6e@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=acme@redhat.com \
--cc=bristot@redhat.com \
--cc=corbet@lwn.net \
--cc=dvhart@vmware.com \
--cc=jbehmer@google.com \
--cc=jolsa@redhat.com \
--cc=julia.lawall@inria.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=tz.stoyanov@gmail.com \
--cc=wagi@monom.org \
--cc=warrier@linux.vnet.ibm.com \
--cc=williams@redhat.com \
--cc=y.karadz@gmail.com \
--cc=zanussi@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
all inboxes | Powered by JetHome®