From: Brian Gerst <brgerst@gmail.com>
To: Tim Blechmann <tim@klingt.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] branch hint tweaks
Date: Tue, 24 Nov 2009 12:50:48 -0500 [thread overview]
Message-ID: <73c1f2160911240950u7256feedqc475fa915dda43ca@mail.gmail.com> (raw)
In-Reply-To: <4B0BBB83.2020604@klingt.org>
On Tue, Nov 24, 2009 at 5:54 AM, Tim Blechmann <tim@klingt.org> wrote:
> hi all,
>
> doing some branch hint profiling of 2.6.31 on my nehalem machine showed
> a few
> incorrect branch hints.
> these patches remove or change the branch hints
>
> Tim Blechmann (5):
> process_64: remove branch hint
> sched.c: change branch hint
> slab.c: remove branch hint
> sched_fair.c: remove branch hint
> workqueue.c: remove branch hint
>
> arch/x86/kernel/process_64.c | 4 ++--
> kernel/sched.c | 4 ++--
> kernel/sched_fair.c | 2 +-
> kernel/workqueue.c | 2 +-
> mm/slab.c | 2 +-
> 5 files changed, 7 insertions(+), 7 deletions(-)
Did you run profiling tests again after making these changes to see if
they had any effect? likely() and unlikely() are only hints. GCC
doesn't have to follow them, or it could be broken in recent GCC
versions.
I'm not sure what version of GCC added this, but I wonder if this
option will fix the problem:
-fno-guess-branch-probability
Do not guess branch probabilities using heuristics.
GCC will use heuristics to guess branch probabilities if they are
not provided by profiling feedback (-fprofile-arcs). These heuristics
are based on the control flow graph. If some branch probabilities are
specified by `__builtin_expect', then the heuristics will be used to
guess branch probabilities for the rest of the control flow graph,
taking the `__builtin_expect' info into account. The interactions
between the heuristics and `__builtin_expect' can be complex, and in
some cases, it may be useful to disable the heuristics so that the
effects of `__builtin_expect' are easier to understand.
The default is -fguess-branch-probability at levels -O, -O2, -O3, -Os.
--
Brian Gerst
next prev parent reply other threads:[~2009-11-24 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-24 10:54 Tim Blechmann
2009-11-24 17:50 ` Brian Gerst [this message]
2009-11-24 18:17 ` Aaron Cohen
2009-11-24 18:59 ` Brian Gerst
2009-11-24 18:21 ` Tim Blechmann
2009-11-24 20:13 ` Brian Gerst
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=73c1f2160911240950u7256feedqc475fa915dda43ca@mail.gmail.com \
--to=brgerst@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim@klingt.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®