From: Ingo Molnar <mingo@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] schedule: use unlikely()
Date: Sat, 25 Nov 2017 09:16:13 +0100 [thread overview]
Message-ID: <20171125081613.damtbce2pelywx2k@gmail.com> (raw)
In-Reply-To: <alpine.LRH.2.02.1711241336410.20259@file01.intranet.prod.int.rdu2.redhat.com>
* Mikulas Patocka <mpatocka@redhat.com> wrote:
>
>
> On Fri, 24 Nov 2017, Ingo Molnar wrote:
>
> > * Mikulas Patocka <mpatocka@redhat.com> wrote:
> >
> > > A small patch for schedule(), so that the code goes straght in the common
> > > case.
> > >
> > > Signed-off-by: Mikulas Patocka <mpatocka@redhat.com>
> > >
> > > ---
> > > include/linux/blkdev.h | 2 +-
> > > kernel/sched/core.c | 2 +-
> > > 2 files changed, 2 insertions(+), 2 deletions(-)
> > >
> > > Index: linux-2.6/include/linux/blkdev.h
> > > ===================================================================
> > > --- linux-2.6.orig/include/linux/blkdev.h
> > > +++ linux-2.6/include/linux/blkdev.h
> > > @@ -1308,7 +1308,7 @@ static inline bool blk_needs_flush_plug(
> > > {
> > > struct blk_plug *plug = tsk->plug;
> > >
> > > - return plug &&
> > > + return unlikely(plug != NULL) &&
> > > (!list_empty(&plug->list) ||
> > > !list_empty(&plug->mq_list) ||
> > > !list_empty(&plug->cb_list));
> >
> > That's an unrelated change.
>
> It is related, because this function gets inlined into schedule().
That needs to be in the changelog and the patch needs to be Cc:-ed to the
affected maintainer as well.
> > > Index: linux-2.6/kernel/sched/core.c
> > > ===================================================================
> > > --- linux-2.6.orig/kernel/sched/core.c
> > > +++ linux-2.6/kernel/sched/core.c
> > > @@ -3405,7 +3405,7 @@ void __noreturn do_task_dead(void)
> > >
> > > static inline void sched_submit_work(struct task_struct *tsk)
> > > {
> > > - if (!tsk->state || tsk_is_pi_blocked(tsk))
> > > + if (!tsk->state || unlikely(tsk_is_pi_blocked(tsk)))
> > > return;
> > > /*
> > > * If we are going to sleep and we have plugged IO queued,
> >
> > Do these changes actually change the generated assembly code?
> >
> > Thanks,
> >
> > Ingo
>
> Yes. It saves two jumps because the compiler falsely assumes that
> tsk_is_pi_blocked would return true. Likewise, the compiler falsely
> assumes that tsk->plug would be true.
>
> The static branch prediction in gcc assumes that pointers are usually not
> NULL, but in this case tsk->pi_blocked_on and tsk->plug are usually NULL.
That too should be in the changelog.
Thanks,
Ingo
next prev parent reply other threads:[~2017-11-25 8:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 19:00 [PATCH] schedule: use unlikely() Mikulas Patocka
2017-11-24 7:38 ` Ingo Molnar
2017-11-24 18:47 ` Mikulas Patocka
2017-11-25 8:16 ` Ingo Molnar [this message]
2017-11-28 3:36 ` Mikulas Patocka
2017-11-25 8:56 ` Greg KH
2017-11-28 0:05 ` Mikulas Patocka
2017-11-28 7:22 ` Greg KH
2017-11-30 7:04 ` Mikulas Patocka
2017-11-30 8:07 ` Greg KH
2017-12-08 14:30 ` Pavel Machek
2017-12-08 14:56 ` Greg KH
2017-12-08 14:29 ` Pavel Machek
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=20171125081613.damtbce2pelywx2k@gmail.com \
--to=mingo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mpatocka@redhat.com \
--cc=peterz@infradead.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