ring-buffer: Make rb_reserve_next_event() always inlined
authorSteven Rostedt (Red Hat) <rostedt@goodmis.org>
Wed, 23 Nov 2016 16:36:30 +0000 (11:36 -0500)
committerSteven Rostedt <rostedt@goodmis.org>
Wed, 23 Nov 2016 16:36:30 +0000 (11:36 -0500)
commitfa7ffb39efccd574163ebc5dbfe4ff066186f261
treee4782a1fae2f735ae3d8ecbda2d37a3e58ee6f1a
parent3e9a8aadca4807b4eadd33a50014c9b2767a4f1f
ring-buffer: Make rb_reserve_next_event() always inlined

The function rb_reserved_next_event() is called by two functions:
ring_buffer_lock_reserve() and ring_buffer_write(). This is in a very hot
path of the tracing code, and it is best that they are not functions. The
two callers are basically wrapers for rb_reserver_next_event(). Removing the
function calls can save execution time in the hotpath of tracing.

Link: http://lkml.kernel.org/r/20161121183700.GW26852@two.firstfloor.org
Reported-by: Andi Kleen <andi@firstfloor.org>
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
kernel/trace/ring_buffer.c