From: Waiman Long <longman@redhat.com>
To: Davidlohr Bueso <dave@stgolabs.net>,
Peter Zijlstra <peterz@infradead.org>
Cc: Yongji Xie <elohimes@gmail.com>,
mingo@redhat.com, will.deacon@arm.com,
linux-kernel@vger.kernel.org, xieyongji@baidu.com,
zhangyu31@baidu.com, liuqi16@baidu.com, yuanlinsi01@baidu.com,
nixun@baidu.com, lilin24@baidu.com,
andrea.parri@amarulasolutions.com
Subject: Re: [PATCH -tip] kernel/sched,wake_q: Branch predict wake_q_add() cmpxchg
Date: Mon, 3 Dec 2018 11:10:58 -0500 [thread overview]
Message-ID: <c1cd0892-9ef4-ffad-ce93-39977389071c@redhat.com> (raw)
In-Reply-To: <20181203053130.gwkw6kg72azt2npb@linux-r8p5>
On 12/03/2018 12:31 AM, Davidlohr Bueso wrote:
> The cmpxchg will fail when the task is already in the process
> of waking up, and as such is an extremely rare occurrence.
> Micro-optimize the call and put an unlikely() around it.
>
> To no surprise, when using CONFIG_PROFILE_ANNOTATED_BRANCHES
> under a number of workloads the incorrect rate was a mere 1-2%.
>
> Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
> ---
> kernel/sched/core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 091e089063be..f7747cf6e427 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -408,7 +408,7 @@ void wake_q_add(struct wake_q_head *head, struct
> task_struct *task)
> * This cmpxchg() executes a full barrier, which pairs with the full
> * barrier executed by the wakeup in wake_up_q().
> */
> - if (cmpxchg(&node->next, NULL, WAKE_Q_TAIL))
> + if (unlikely(cmpxchg(&node->next, NULL, WAKE_Q_TAIL)))
> return;
>
> get_task_struct(task);
Acked-by: Waiman Long <longman@redhat.com>
next prev parent reply other threads:[~2018-12-03 16:11 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 12:50 [RFC] locking/rwsem: Avoid issuing wakeup before setting the reader waiter to nil Yongji Xie
2018-11-29 13:12 ` Peter Zijlstra
2018-11-29 13:44 ` Peter Zijlstra
2018-11-29 14:02 ` Yongji Xie
2018-11-29 18:43 ` Davidlohr Bueso
2018-11-29 18:49 ` Waiman Long
2018-11-29 15:21 ` Waiman Long
2018-11-29 15:29 ` Waiman Long
2018-11-29 16:06 ` Peter Zijlstra
2018-11-29 17:02 ` Waiman Long
2018-11-29 17:27 ` Peter Zijlstra
2018-11-29 17:58 ` Waiman Long
2018-11-29 18:13 ` Peter Zijlstra
2018-11-29 18:17 ` Davidlohr Bueso
2018-11-29 18:08 ` Peter Zijlstra
2018-11-29 18:26 ` Waiman Long
2018-11-29 18:31 ` Will Deacon
2018-11-29 18:34 ` Waiman Long
2018-11-29 22:05 ` Peter Zijlstra
2018-11-30 9:34 ` 答复: " Liu,Qi(ACU-T1)
2018-11-30 14:15 ` Peter Zijlstra
2018-11-29 21:30 ` Davidlohr Bueso
2018-11-29 21:34 ` Davidlohr Bueso
2018-11-29 22:17 ` Peter Zijlstra
2018-11-30 9:30 ` Andrea Parri
2018-12-03 5:31 ` [PATCH -tip] kernel/sched,wake_q: Branch predict wake_q_add() cmpxchg Davidlohr Bueso
2018-12-03 16:10 ` Waiman Long [this message]
2019-01-21 11:28 ` [tip:locking/core] sched/wake_q: Add branch prediction hint to " tip-bot for Davidlohr Bueso
2018-12-10 15:12 ` [RFC] locking/rwsem: Avoid issuing wakeup before setting the reader waiter to nil Yongji Xie
2018-12-17 11:37 ` Peter Zijlstra
2018-12-17 13:12 ` Yongji Xie
2019-01-07 14:35 ` Waiman Long
2019-01-07 15:31 ` Peter Zijlstra
2019-01-07 15:35 ` Waiman Long
2018-12-17 20:53 ` Davidlohr Bueso
2018-12-18 13:10 ` Peter Zijlstra
2018-12-18 13:14 ` Peter Zijlstra
2018-12-18 17:27 ` Davidlohr Bueso
2018-12-18 18:54 ` [PATCH v2] sched/wake_q: Reduce reference counting for special users Davidlohr Bueso
2018-12-18 19:17 ` Waiman Long
2018-12-18 19:30 ` Davidlohr Bueso
2018-12-18 19:39 ` Davidlohr Bueso
2018-12-18 19:53 ` [PATCH v4] " Davidlohr Bueso
2018-12-18 20:35 ` Waiman Long
2019-01-21 16:02 ` Davidlohr Bueso
2019-01-22 8:55 ` Peter Zijlstra
2019-02-04 8:57 ` [tip:locking/core] " tip-bot for Davidlohr Bueso
2019-02-07 19:30 ` Davidlohr Bueso
2019-02-12 14:14 ` Daniel Vacek
2019-01-21 11:28 ` [tip:locking/core] locking/rwsem: Fix (possible) missed wakeup tip-bot for Xie Yongji
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=c1cd0892-9ef4-ffad-ce93-39977389071c@redhat.com \
--to=longman@redhat.com \
--cc=andrea.parri@amarulasolutions.com \
--cc=dave@stgolabs.net \
--cc=elohimes@gmail.com \
--cc=lilin24@baidu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=liuqi16@baidu.com \
--cc=mingo@redhat.com \
--cc=nixun@baidu.com \
--cc=peterz@infradead.org \
--cc=will.deacon@arm.com \
--cc=xieyongji@baidu.com \
--cc=yuanlinsi01@baidu.com \
--cc=zhangyu31@baidu.com \
/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;
as well as URLs for NNTP newsgroup(s).