From: Tim Blechmann <tim@klingt.org>
To: linux-kernel@vger.kernel.org
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] sched: Optimize branch hint in context_switch()
Date: Sun, 29 Nov 2009 17:02:51 +0100 [thread overview]
Message-ID: <4B129B2B.1040309@klingt.org> (raw)
In-Reply-To: <4B129277.5050000@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 2003 bytes --]
On 11/29/2009 04:25 PM, Avi Kivity wrote:
> On 11/29/2009 05:20 PM, Peter Zijlstra wrote:
>> On Sun, 2009-11-29 at 17:12 +0200, Avi Kivity wrote:
>>
>>> On 11/29/2009 02:01 PM, Tim Blechmann wrote:
>>>
>>>> Branch hint profiling on my nehalem machine showed 88%
>>>> incorrect branch hints:
>>>>
>>>> 42017484 326957902 88 context_switch sched.c 3043
>>>> 42038493 326953687 88 context_switch sched.c 3050
>>>>
>>>> @@ -3040,14 +3040,14 @@ context_switch(struct rq *rq, struct task_struct *prev,
>>>> */
>>>> arch_start_context_switch(prev);
>>>>
>>>> - if (likely(!mm)) {
>>>> + if (unlikely(!mm)) {
>>>> next->active_mm = oldmm;
>>>> atomic_inc(&oldmm->mm_count);
>>>> enter_lazy_tlb(oldmm, next);
>>>> } else
>>>> switch_mm(oldmm, mm, next);
>>>>
>>>> - if (likely(!prev->mm)) {
>>>> + if (unlikely(!prev->mm)) {
>>>> prev->active_mm = NULL;
>>>> rq->prev_mm = oldmm;
>>>> }
>>>>
>>>>
>>> I don't think either the original or the patch is correct. Whether or
>>> not a task has an mm is entirely workload dependent, we shouldn't be
>>> giving hints here.
>>>
>> There are reasons to still use branch hints, for example if the unlikely
>> branch is very expensive anyway and it pays to have the likely branch be
>> ever so slightly less expensive.
>>
>> Now I don't think that applies here, but there are cases where such code
>> generation issues are the main motivator not the actual usage patterns.
would be nice, if you commit a patch, removing this hint
> These should be documented then to avoid patches removing them:
>
> #define slowpath(x) unlikely(x)
>
> if (slowpath(condition))
> expensive_operation();
this would definitely improve the expressive power ...
thnx, tim
--
tim@klingt.org
http://tim.klingt.org
Only very good and very bad programmers use goto in C
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-11-29 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 12:01 [PATCH] sched: Optimize branch hint in context_switch() Tim Blechmann
2009-11-29 15:12 ` Avi Kivity
2009-11-29 15:20 ` Peter Zijlstra
2009-11-29 15:25 ` Avi Kivity
2009-11-29 16:02 ` Tim Blechmann [this message]
2009-11-30 9:25 ` Christian Borntraeger
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=4B129B2B.1040309@klingt.org \
--to=tim@klingt.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.