From: Torsten Duwe <duwe@lst.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Tom Musta <tommusta@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>,
Scott Wood <scottwood@freescale.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
linuxppc-dev@lists.ozlabs.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH v2] powerpc ticket locks
Date: Mon, 10 Feb 2014 16:52:17 +0100 [thread overview]
Message-ID: <20140210155217.GF2107@lst.de> (raw)
In-Reply-To: <1392001823.3996.21.camel@pasglop>
On Mon, Feb 10, 2014 at 02:10:23PM +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2014-02-07 at 17:58 +0100, Torsten Duwe wrote:
> > typedef struct {
> > - volatile unsigned int slock;
> > -} arch_spinlock_t;
> > + union {
> > + __ticketpair_t head_tail;
> > + struct __raw_tickets {
> > +#ifdef __BIG_ENDIAN__ /* The "tail" part should be in the MSBs */
> > + __ticket_t tail, head;
> > +#else
> > + __ticket_t head, tail;
> > +#endif
> > + } tickets;
> > + };
> > +#if defined(CONFIG_PPC_SPLPAR)
> > + u32 holder;
> > +#endif
> > +} arch_spinlock_t __aligned(4);
>
> That's still broken with lockref (which we just merged).
>
> We must have the arch_spinlock_t and the ref in the same 64-bit word
> otherwise it will break.
Well, as far as I can see you'll just not be able to
USE_CMPXCHG_LOCKREF -- with the appropriate performance hit --
the code just falls back into lock&ref on pSeries.
What again was the intention of directed yield in the first place...?
> We can make it work in theory since the holder doesn't have to be
> accessed atomically, but the practicals are a complete mess ...
> lockref would essentially have to re-implement the holder handling
> of the spinlocks and use lower level ticket stuff.
>
> Unless you can find a sneaky trick ... :-(
What if I squeeze the bits a little?
4k vCPUs, and 256 physical, as a limit to stay within 32 bits?
At the cost that unlock may become an ll/sc operation again.
I could think about a trick against that.
But alas, hw_cpu_id is 16 bit, which makes a lookup table neccessary :-/
Doing another round of yields for lockrefs now doesn't
sound so bad any more.
Opinions, anyone?
Torsten
WARNING: multiple messages have this Message-ID (diff)
From: Torsten Duwe <duwe@lst.de>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Paul Mackerras <paulus@samba.org>,
Anton Blanchard <anton@samba.org>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Peter Zijlstra <peterz@infradead.org>,
Scott Wood <scottwood@freescale.com>,
Tom Musta <tommusta@gmail.com>, Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc ticket locks
Date: Mon, 10 Feb 2014 16:52:17 +0100 [thread overview]
Message-ID: <20140210155217.GF2107@lst.de> (raw)
In-Reply-To: <1392001823.3996.21.camel@pasglop>
On Mon, Feb 10, 2014 at 02:10:23PM +1100, Benjamin Herrenschmidt wrote:
> On Fri, 2014-02-07 at 17:58 +0100, Torsten Duwe wrote:
> > typedef struct {
> > - volatile unsigned int slock;
> > -} arch_spinlock_t;
> > + union {
> > + __ticketpair_t head_tail;
> > + struct __raw_tickets {
> > +#ifdef __BIG_ENDIAN__ /* The "tail" part should be in the MSBs */
> > + __ticket_t tail, head;
> > +#else
> > + __ticket_t head, tail;
> > +#endif
> > + } tickets;
> > + };
> > +#if defined(CONFIG_PPC_SPLPAR)
> > + u32 holder;
> > +#endif
> > +} arch_spinlock_t __aligned(4);
>
> That's still broken with lockref (which we just merged).
>
> We must have the arch_spinlock_t and the ref in the same 64-bit word
> otherwise it will break.
Well, as far as I can see you'll just not be able to
USE_CMPXCHG_LOCKREF -- with the appropriate performance hit --
the code just falls back into lock&ref on pSeries.
What again was the intention of directed yield in the first place...?
> We can make it work in theory since the holder doesn't have to be
> accessed atomically, but the practicals are a complete mess ...
> lockref would essentially have to re-implement the holder handling
> of the spinlocks and use lower level ticket stuff.
>
> Unless you can find a sneaky trick ... :-(
What if I squeeze the bits a little?
4k vCPUs, and 256 physical, as a limit to stay within 32 bits?
At the cost that unlock may become an ll/sc operation again.
I could think about a trick against that.
But alas, hw_cpu_id is 16 bit, which makes a lookup table neccessary :-/
Doing another round of yields for lockrefs now doesn't
sound so bad any more.
Opinions, anyone?
Torsten
next prev parent reply other threads:[~2014-02-10 15:52 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 16:58 [PATCH v2] powerpc ticket locks Torsten Duwe
2014-02-07 16:58 ` Torsten Duwe
2014-02-07 17:12 ` Peter Zijlstra
2014-02-07 17:12 ` Peter Zijlstra
2014-02-07 17:55 ` Torsten Duwe
2014-02-07 17:55 ` Torsten Duwe
2014-02-10 3:10 ` Benjamin Herrenschmidt
2014-02-10 3:10 ` Benjamin Herrenschmidt
2014-02-10 15:52 ` Torsten Duwe [this message]
2014-02-10 15:52 ` Torsten Duwe
2014-02-10 17:53 ` Peter Zijlstra
2014-02-10 17:53 ` Peter Zijlstra
2014-02-11 2:44 ` Benjamin Herrenschmidt
2014-02-11 2:44 ` Benjamin Herrenschmidt
2014-02-11 2:56 ` Al Viro
2014-02-11 2:56 ` Al Viro
2014-02-11 3:38 ` Benjamin Herrenschmidt
2014-02-11 3:38 ` Benjamin Herrenschmidt
2014-02-11 9:53 ` Raghavendra KT
2014-02-11 9:53 ` Raghavendra KT
2014-02-11 10:40 ` Torsten Duwe
2014-02-11 10:40 ` Torsten Duwe
2014-02-11 18:30 ` Scott Wood
2014-02-11 18:30 ` Scott Wood
2014-02-11 19:34 ` Benjamin Herrenschmidt
2014-02-11 19:34 ` Benjamin Herrenschmidt
2014-02-11 9:39 ` Raghavendra KT
2014-02-11 9:39 ` Raghavendra KT
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=20140210155217.GF2107@lst.de \
--to=duwe@lst.de \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=paulus@samba.org \
--cc=peterz@infradead.org \
--cc=scottwood@freescale.com \
--cc=tommusta@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.