From: Ingo Molnar <mingo@elte.hu>
To: Jason Baron <jbaron@redhat.com>
Cc: linux-kernel@vger.kernel.org, fweisbec@gmail.com,
laijs@cn.fujitsu.com, rostedt@goodmis.org, peterz@infradead.org,
mathieu.desnoyers@polymtl.ca, jiayingz@google.com,
mbligh@google.com, roland@redhat.com, fche@redhat.com
Subject: Re: [PATCH 0/3] tracepoints: delay argument evaluation
Date: Wed, 20 May 2009 09:33:48 +0200 [thread overview]
Message-ID: <20090520073348.GA12316@elte.hu> (raw)
In-Reply-To: <cover.1242763826.git.jbaron@redhat.com>
* Jason Baron <jbaron@redhat.com> wrote:
> hi,
>
> After disassembling some of the tracepoints, I've noticed that
> arguments that are passed as macros or that perform dereferences,
> evaluate prior to the tracepoint on/off check. This means that we
> are needlessly impacting the off case.
>
> I am proposing to fix this by adding a macro that first checks for
> on/off and then calls 'trace_##name', preserving type checking.
> Thus, callsites have to move from:
>
> trace_block_bio_complete(md->queue, bio);
>
> to:
>
> tracepoint_call(block_bio_complete, md->queue, bio);
>
> I've tried '__always_inline', but that did not fix this issue.
> Obviously this change will require changes to all the callsites.
> But, that shouldn't be very hard, I've already included the
> scheduler and block changes with this patch. I think its important
> to minimize code execution in the off case, and thus going through
> all the callsites is well worth it. If we agree on this change, I
> can change the rest in very short order.
>
> Below I'm also showing the assembly in the 'dec_pending()'
> function before and after this change to show the difference it
> makes. The arguments to the tracepoint are as above, 'md->queue'
> and 'bio'. Notice the 2 extra instructions, before the initial
> 'je', that could be moved after the 'je'.
>
> before:
>
> ffffffff8137b2a3: 83 3d de 90 4b 00 00 cmpl $0x0,0x4b90de(%rip) # ffffffff81834388 <__tracepoint_block_bio_complete+0x8>
> ffffffff8137b2aa: 49 8b 45 50 mov 0x50(%r13),%rax
> ffffffff8137b2ae: 48 89 45 d0 mov %rax,-0x30(%rbp)
> ffffffff8137b2b2: 74 1f je ffffffff8137b2d3 <dec_pending+0x101>
> after:
>
> ffffffff8137b2a3: 83 3d de 90 4b 00 00 cmpl $0x0,0x4b90de(%rip) # ffffffff81834388 <__tracepoint_block_bio_complete+0x8>
> ffffffff8137b2aa: 74 27 je ffffffff8137b2d3 <dec_pending+0x101>
hm, this is really a compiler bug in essence - the compiler should
delay the construction of arguments into unlikely branches - if the
arguments are only used there.
We'd basically open-code a clear-cut:
trace_block_bio_complete(md->queue, bio);
into this form:
trace(block_bio_complete, md->queue, bio);
.. and this latter form could become moot (and a nuisance) if the
compiler is fixed.
Have you tried very latest GCC, does it still have this optimization
problem?
Note that the compiler getting this right would help a _lot_ of
other inline functions in the kernel as well. Arguments only used
within unlikely() branches are quite common.
Ingo
next prev parent reply other threads:[~2009-05-20 7:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 21:03 Jason Baron
2009-05-19 21:03 ` [PATCH 1/3] tracepoints: add tracepoint_call() to optimize tracepoints disabled Jason Baron
2009-05-19 21:03 ` [PATCH 2/3] tracepoints: convert scheduler tracepoints to 'tracepoint_call' api Jason Baron
2009-05-19 21:03 ` [PATCH 3/3] tracepoints: convert block " Jason Baron
2009-05-19 21:17 ` [PATCH 0/3] tracepoints: delay argument evaluation Mathieu Desnoyers
2009-05-19 22:16 ` Jason Baron
2009-05-19 22:25 ` Roland McGrath
2009-05-19 22:31 ` Steven Rostedt
2009-05-19 22:36 ` Steven Rostedt
2009-05-19 23:52 ` Frederic Weisbecker
2009-05-20 0:33 ` Mathieu Desnoyers
2009-05-20 0:42 ` Steven Rostedt
2009-05-20 7:01 ` Roland McGrath
2009-05-20 7:12 ` Peter Zijlstra
[not found] ` <20090520072750.DA9A0FC38D@magilla.sf.frob.com>
2009-05-20 7:38 ` Peter Zijlstra
2009-05-20 9:18 ` Roland McGrath
2009-05-20 7:33 ` Ingo Molnar [this message]
2009-05-20 15:42 ` Jason Baron
2009-05-21 1:49 ` Jiaying Zhang
2009-05-21 1:59 ` Li Zefan
2009-05-21 2:15 ` Jiaying Zhang
2009-05-21 2:41 ` Li Zefan
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=20090520073348.GA12316@elte.hu \
--to=mingo@elte.hu \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=jiayingz@google.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@google.com \
--cc=peterz@infradead.org \
--cc=roland@redhat.com \
--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
Powered by JetHome