From: Waiman Long <longman@redhat.com>
To: Qiuxu Zhuo <qiuxu.zhuo@intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Will Deacon <will@kernel.org>
Cc: Boqun Feng <boqun.feng@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] locking/qspinlock: Make the 1st spinner only spin on locked_pending bits
Date: Mon, 8 May 2023 11:31:18 -0400 [thread overview]
Message-ID: <29297e16-2c79-8367-cd6c-efedd0a8d9ed@redhat.com> (raw)
In-Reply-To: <20230508081532.36379-1-qiuxu.zhuo@intel.com>
On 5/8/23 04:15, Qiuxu Zhuo wrote:
> The 1st spinner (header of the MCS queue) spins on the whole qspinlock
> variable to check whether the lock is released. For a contended qspinlock,
> this spinning is a hotspot as each CPU queued in the MCS queue performs
> the spinning when it becomes the 1st spinner (header of the MCS queue).
>
> The granularity among SMT h/w threads in the same core could be "byte"
> which the Load-Store Unit (LSU) inside the core handles. Making the 1st
> spinner only spin on locked_pending bits (not the whole qspinlock) can
> avoid the false dependency between the tail field and the locked_pending
> field. So this micro-optimization helps the h/w thread (the 1st spinner)
> stay in a low power state and prevents it from being woken up by other
> h/w threads in the same core when they perform xchg_tail() to update
> the tail field. Please see a similar discussion in the link [1].
>
> [1] https://lore.kernel.org/r/20230105021952.3090070-1-guoren@kernel.org
>
> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
> ---
> kernel/locking/qspinlock.c | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
> index efebbf19f887..e7b990b28610 100644
> --- a/kernel/locking/qspinlock.c
> +++ b/kernel/locking/qspinlock.c
> @@ -513,7 +513,20 @@ void __lockfunc queued_spin_lock_slowpath(struct qspinlock *lock, u32 val)
> if ((val = pv_wait_head_or_lock(lock, node)))
> goto locked;
>
> +#if _Q_PENDING_BITS == 8
> + /*
> + * Spinning on the 2-byte locked_pending instead of the 4-byte qspinlock
> + * variable can avoid the false dependency between the tail field and
> + * the locked_pending field. This helps the h/w thread (the 1st spinner)
> + * stay in a low power state and prevents it from being woken up by other
> + * h/w threads in the same core when they perform xchg_tail() to update
> + * the tail field only.
> + */
> + smp_cond_load_acquire(&lock->locked_pending, !VAL);
> + val = atomic_read_acquire(&lock->val);
> +#else
> val = atomic_cond_read_acquire(&lock->val, !(VAL & _Q_LOCKED_PENDING_MASK));
> +#endif
>
> locked:
> /*
What hardware can benefit from this change? Do you have any
micro-benchmark that can show the performance benefit?
Cheers,
Longman
next prev parent reply other threads:[~2023-05-08 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 8:15 Qiuxu Zhuo
2023-05-08 15:31 ` Waiman Long [this message]
2023-05-09 2:45 ` Zhuo, Qiuxu
2023-05-09 2:57 ` Waiman Long
2023-05-09 3:30 ` Zhuo, Qiuxu
2023-05-09 14:33 ` Waiman Long
2023-05-15 6:42 ` kernel test robot
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=29297e16-2c79-8367-cd6c-efedd0a8d9ed@redhat.com \
--to=longman@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=qiuxu.zhuo@intel.com \
--cc=will@kernel.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®