From: Peter Zijlstra <peterz@infradead.org>
To: guoren@kernel.org
Cc: palmer@rivosinc.com, arnd@arndb.de, mingo@redhat.com,
will@kernel.org, longman@redhat.com, boqun.feng@gmail.com,
linux-riscv@lists.infradead.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, Guo Ren <guoren@linux.alibaba.com>
Subject: Re: [PATCH V7 4/5] asm-generic: spinlock: Add combo spinlock (ticket & queued)
Date: Mon, 4 Jul 2022 11:57:55 +0200 [thread overview]
Message-ID: <YsK5o8eiVHeS+7Iw@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20220628081707.1997728-5-guoren@kernel.org>
On Tue, Jun 28, 2022 at 04:17:06AM -0400, guoren@kernel.org wrote:
> From: Guo Ren <guoren@linux.alibaba.com>
>
> Some architecture has a flexible requirement on the type of spinlock.
> Some LL/SC architectures of ISA don't force micro-arch to give a strong
> forward guarantee. Thus different kinds of memory model micro-arch would
> come out in one ISA. The ticket lock is suitable for exclusive monitor
> designed LL/SC micro-arch with limited cores and "!NUMA". The
> queue-spinlock could deal with NUMA/large-scale scenarios with a strong
> forward guarantee designed LL/SC micro-arch.
>
> So, make the spinlock a combo with feature.
>
> Signed-off-by: Guo Ren <guoren@linux.alibaba.com>
> Signed-off-by: Guo Ren <guoren@kernel.org>
> Cc: Peter Zijlstra (Intel) <peterz@infradead.org>
> Cc: Arnd Bergmann <arnd@arndb.de>
> Cc: Palmer Dabbelt <palmer@rivosinc.com>
> ---
> include/asm-generic/spinlock.h | 43 ++++++++++++++++++++++++++++++++--
> kernel/locking/qspinlock.c | 2 ++
> 2 files changed, 43 insertions(+), 2 deletions(-)
>
> diff --git a/include/asm-generic/spinlock.h b/include/asm-generic/spinlock.h
> index f41dc7c2b900..a9b43089bf99 100644
> --- a/include/asm-generic/spinlock.h
> +++ b/include/asm-generic/spinlock.h
> @@ -28,34 +28,73 @@
> #define __ASM_GENERIC_SPINLOCK_H
>
> #include <asm-generic/ticket_spinlock.h>
> +#ifdef CONFIG_ARCH_USE_QUEUED_SPINLOCKS
> +#include <linux/jump_label.h>
> +#include <asm-generic/qspinlock.h>
> +
> +DECLARE_STATIC_KEY_TRUE(use_qspinlock_key);
> +#endif
> +
> +#undef arch_spin_is_locked
> +#undef arch_spin_is_contended
> +#undef arch_spin_value_unlocked
> +#undef arch_spin_lock
> +#undef arch_spin_trylock
> +#undef arch_spin_unlock
>
> static __always_inline void arch_spin_lock(arch_spinlock_t *lock)
> {
> - ticket_spin_lock(lock);
> +#ifdef CONFIG_ARCH_USE_QUEUED_SPINLOCKS
> + if (static_branch_likely(&use_qspinlock_key))
> + queued_spin_lock(lock);
> + else
> +#endif
> + ticket_spin_lock(lock);
> }
>
> static __always_inline bool arch_spin_trylock(arch_spinlock_t *lock)
> {
> +#ifdef CONFIG_ARCH_USE_QUEUED_SPINLOCKS
> + if (static_branch_likely(&use_qspinlock_key))
> + return queued_spin_trylock(lock);
> +#endif
> return ticket_spin_trylock(lock);
> }
>
> static __always_inline void arch_spin_unlock(arch_spinlock_t *lock)
> {
> - ticket_spin_unlock(lock);
> +#ifdef CONFIG_ARCH_USE_QUEUED_SPINLOCKS
> + if (static_branch_likely(&use_qspinlock_key))
> + queued_spin_unlock(lock);
> + else
> +#endif
> + ticket_spin_unlock(lock);
> }
>
> static __always_inline int arch_spin_is_locked(arch_spinlock_t *lock)
> {
> +#ifdef CONFIG_ARCH_USE_QUEUED_SPINLOCKS
> + if (static_branch_likely(&use_qspinlock_key))
> + return queued_spin_is_locked(lock);
> +#endif
> return ticket_spin_is_locked(lock);
> }
>
> static __always_inline int arch_spin_is_contended(arch_spinlock_t *lock)
> {
> +#ifdef CONFIG_ARCH_USE_QUEUED_SPINLOCKS
> + if (static_branch_likely(&use_qspinlock_key))
> + return queued_spin_is_contended(lock);
> +#endif
> return ticket_spin_is_contended(lock);
> }
>
> static __always_inline int arch_spin_value_unlocked(arch_spinlock_t lock)
> {
> +#ifdef CONFIG_ARCH_USE_QUEUED_SPINLOCKS
> + if (static_branch_likely(&use_qspinlock_key))
> + return queued_spin_value_unlocked(lock);
> +#endif
> return ticket_spin_value_unlocked(lock);
> }
Urggghhhh....
I really don't think you want this in generic code. Also, I'm thinking
any arch that does this wants to make sure it doesn't inline any of this
stuff. That is, said arch must not have ARCH_INLINE_SPIN_*
And if you're going to force things out of line, then I think you can
get better code using static_call().
*shudder*...
next prev parent reply other threads:[~2022-07-04 9:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 8:17 [PATCH V7 0/5] riscv: Add qspinlock support with combo style guoren
2022-06-28 8:17 ` [PATCH V7 1/5] asm-generic: ticket-lock: Remove unnecessary atomic_read guoren
2022-06-28 18:05 ` Waiman Long
2022-06-29 2:12 ` Guo Ren
2022-06-29 8:27 ` David Laight
2022-07-01 15:18 ` Guo Ren
2022-07-04 9:52 ` Peter Zijlstra
2022-07-04 11:10 ` Guo Ren
2022-06-28 8:17 ` [PATCH V7 2/5] asm-generic: ticket-lock: Use the same struct definitions with qspinlock guoren
2022-06-28 8:17 ` [PATCH V7 3/5] asm-generic: ticket-lock: Move into ticket_spinlock.h guoren
2022-06-28 8:17 ` [PATCH V7 4/5] asm-generic: spinlock: Add combo spinlock (ticket & queued) guoren
2022-06-28 18:13 ` Waiman Long
2022-06-29 1:17 ` Guo Ren
2022-06-29 1:34 ` Waiman Long
2022-06-29 2:29 ` Guo Ren
2022-06-29 7:08 ` Arnd Bergmann
2022-06-29 8:24 ` Guo Ren
2022-06-29 8:29 ` Arnd Bergmann
2022-07-01 12:18 ` Guo Ren
2022-06-29 12:53 ` Waiman Long
2022-07-04 9:57 ` Peter Zijlstra [this message]
2022-07-04 13:13 ` Guo Ren
2022-07-04 13:45 ` Peter Zijlstra
2022-06-28 8:17 ` [PATCH V7 5/5] riscv: Add qspinlock support guoren
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=YsK5o8eiVHeS+7Iw@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arnd@arndb.de \
--cc=boqun.feng@gmail.com \
--cc=guoren@kernel.org \
--cc=guoren@linux.alibaba.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=palmer@rivosinc.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