Re: [RFC PATCH 00/16] Remove unused arch_*_relax operations from spinlocks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Jun 28, 2013 at 08:31:03AM +0100, Martin Schwidefsky wrote:
> On Mon, 24 Jun 2013 12:58:25 +0100
> Will Deacon <will.deacon@xxxxxxx> wrote:
> > With GENERIC_LOCKBREAK (arm64, ia64, m32r, parisc, powerpc, s390, sh and
> > sparc), we can actually spit out arch_*_relax calls in kernel/spinlock.c
> > using some macro concatenation that defeated my grep-fu.
> > 
> > This only makes a difference on powerpc and s390, so we could either:
> > 
> >   (1) conditionally define the relax macros as cpu_relax in spinlock.c (so
> >       the two guys above can have their special versions)
> > 
> >   (2) Replace the calls with calls to cpu_relax() (although powerpc seems to
> >       want to know who owns the lock in order to relax)
> > 
> >   (3) Leave the current code alone for architectures that may select
> >       GENERIC_LOCKBREAK
> > 
> > Any other ideas/preferences?
> 
> Yeah, we never came around to implement arch_read/write_relax. We can remove
> the two defines for s390, if we want to add some logic there we can just re-add
> an appropriate definition. As powerpc is optimizing their read/write locks
> with GENERIC_LOCKBREAK=y we should leave the ability to override the relax
> function as it is, no?

Yes, I'll drop the powerpc patch and then add the following patch to the
start of the series for v2.

Cheers,

Will

--->8

>From 87707347c9239b647c3b1dd57063eac08fdb1bf4 Mon Sep 17 00:00:00 2001
From: Will Deacon <will.deacon@xxxxxxx>
Date: Mon, 24 Jun 2013 19:06:51 +0100
Subject: [PATCH] locking: add default arch_*_relax definitions for
 GENERIC_LOCKBREAK

When running with GENERIC_LOCKBREAK=y, the locking implementations emit
calls to arch_{read,write,spin}_relax when spinning on a contended lock
in order to allow architectures to favour the CPU owning the lock if
possible.

In reality, everybody apart from PowerPC and S390 just does cpu_relax()
here, so make that the default behaviour and allow it to be overridden
if required.

Cc: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
Cc: Martin Schwidefsky <schwidefsky@xxxxxxxxxx>
Cc: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Signed-off-by: Will Deacon <will.deacon@xxxxxxx>
---
 kernel/spinlock.c | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/kernel/spinlock.c b/kernel/spinlock.c
index 5cdd806..4b082b5 100644
--- a/kernel/spinlock.c
+++ b/kernel/spinlock.c
@@ -34,6 +34,20 @@
 #else
 #define raw_read_can_lock(l)	read_can_lock(l)
 #define raw_write_can_lock(l)	write_can_lock(l)
+
+/*
+ * Some architectures can relax in favour of the CPU owning the lock.
+ */
+#ifndef arch_read_relax
+# define arch_read_relax(l)	cpu_relax()
+#endif
+#ifndef arch_write_relax
+# define arch_write_relax(l)	cpu_relax()
+#endif
+#ifndef arch_spin_relax
+# define arch_spin_relax(l)	cpu_relax()
+#endif
+
 /*
  * We build the __lock_function inlines here. They are too large for
  * inlining all over the place, but here is only one user per function
-- 
1.8.2.2

--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Kernel Newbies]     [x86 Platform Driver]     [Netdev]     [Linux Wireless]     [Netfilter]     [Bugtraq]     [Linux Filesystems]     [Yosemite Discussion]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Device Mapper]

  Powered by Linux