From: Waiman Long <longman@redhat.com>
To: guoren@kernel.org, peterz@infradead.org, mingo@redhat.com
Cc: linux-kernel@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>,
Boqun Feng <boqun.feng@gmail.com>, Will Deacon <will@kernel.org>
Subject: Re: [PATCH V2] locking/qspinlock: Optimize pending state waiting for unlock
Date: Wed, 4 Jan 2023 22:34:54 -0500 [thread overview]
Message-ID: <fd3ae111-7b4b-ebe9-82a2-42beaaf02157@redhat.com> (raw)
In-Reply-To: <20230105021952.3090070-1-guoren@kernel.org>
On 1/4/23 21:19, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> When we're pending, we only care about lock value. The xchg_tail
> wouldn't affect the pending state. That means the hardware thread
> could stay in a sleep state and leaves the rest execution units'
> resources of pipeline to other hardware threads. This situation is
> the SMT scenarios in the same core. Not an entering low-power state
> situation. Of course, the granularity between cores is "cacheline",
> but the granularity between SMT hw threads of the same core could
> be "byte" which internal LSU handles. For example, when a hw-thread
> yields the resources of the core to other hw-threads, this patch
> could help the hw-thread stay in the sleep state and prevent it
> from being woken up by other hw-threads xchg_tail.
>
> Link: https://lore.kernel.org/lkml/20221224120545.262989-1-guoren@kernel.org/
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> Acked-by: Waiman Long <longman@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Boqun Feng <boqun.feng@gmail.com>
> Cc: Will Deacon <will@kernel.org>
> Cc: Ingo Molnar <mingo@redhat.com>
> ---
> Changes in v2:
> - Add acked tag
> - Optimize commit log
> - Add discussion Link tag
> ---
> kernel/locking/qspinlock.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/kernel/locking/qspinlock.c b/kernel/locking/qspinlock.c
> index 2b23378775fe..ebe6b8ec7cb3 100644
> --- a/kernel/locking/qspinlock.c
> +++ b/kernel/locking/qspinlock.c
> @@ -371,7 +371,7 @@ void __lockfunc queued_spin_lock_slowpath(struct qspinlock *lock, u32 val)
> /*
> * We're pending, wait for the owner to go away.
> *
> - * 0,1,1 -> 0,1,0
> + * 0,1,1 -> *,1,0
> *
> * this wait loop must be a load-acquire such that we match the
> * store-release that clears the locked bit and create lock
> @@ -380,7 +380,7 @@ void __lockfunc queued_spin_lock_slowpath(struct qspinlock *lock, u32 val)
> * barriers.
> */
> if (val & _Q_LOCKED_MASK)
> - atomic_cond_read_acquire(&lock->val, !(VAL & _Q_LOCKED_MASK));
> + smp_cond_load_acquire(&lock->locked, !VAL);
>
> /*
> * take ownership and clear the pending bit.
Yes, the new patch description looks good to me. Thank for sending the v2.
Cheers,
Longman
next prev parent reply other threads:[~2023-01-05 3:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 2:19 [PATCH V2] locking/qspinlock: Optimize pending state waiting for unlock guoren
2023-01-05 3:34 ` Waiman Long [this message]
2023-01-05 10:36 ` [tip: locking/core] locking/qspinlock: Micro-optimize " tip-bot2 for Guo Ren
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=fd3ae111-7b4b-ebe9-82a2-42beaaf02157@redhat.com \
--to=longman@redhat.com \
--cc=boqun.feng@gmail.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--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