From: Peter Zijlstra <peterz@infradead.org>
To: Waiman Long <waiman.long@hp.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] asm-generic implementations of low-level synchronisation constructs
Date: Wed, 7 May 2014 23:26:26 +0200 [thread overview]
Message-ID: <20140507212626.GD2844@laptop.programming.kicks-ass.net> (raw)
In-Reply-To: <536AA2FC.6070006@hp.com>
On Wed, May 07, 2014 at 05:17:48PM -0400, Waiman Long wrote:
> On 05/07/2014 02:29 PM, Will Deacon wrote:
> >Hi all,
> >
> >Traditionally, low-level synchronisation and atomic constructs have been
> >buried away in arch-specific code, with new arch maintainers having to
> >wrestle with Documentation/{memory-barriers,atomic_ops}.txt to ensure
> >they provide the (somewhat arbitrary) semantics expected by the kernel.
> >
> >However, over the past year, there have been some notable events in this
> >area:
> >
> > (1) The addition of smp_load_acquire/smp_store_release across all
> > architectures (including asm-generic)
> > https://lwn.net/Articles/576486/
> >
> > (2) Merging of generic MCS spinlocks into kernel/locking, built using
> > the macros introduced by (1). There are other similar patches for
> > queued spinlocks and rwlocks, but they're not completely generic
> > afaict.
> > http://lwn.net/Articles/590243/
>
> It is true that the current qspinlock patch is not completely generic.
> However, I think it can still be used by most architectures with the
> exception of, perhaps just, the pre-EV56 alpha.
Its going to be a massive pain on virt archs like PPC and s390. So while
those archs don't suffer the same problem Alpha does, they have problem
with fair locks.
next prev parent reply other threads:[~2014-05-07 21:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-07 18:29 Will Deacon
2014-05-07 19:12 ` Peter Zijlstra
2014-05-07 21:20 ` Will Deacon
2014-05-08 9:13 ` Peter Zijlstra
2014-05-08 14:27 ` Peter Zijlstra
2014-05-08 14:43 ` David Woodhouse
2014-05-08 15:13 ` Will Deacon
2014-05-08 16:39 ` Paul E. McKenney
2014-05-07 21:17 ` Waiman Long
2014-05-07 21:26 ` Peter Zijlstra [this message]
2014-05-07 22:29 ` Waiman Long
2014-05-08 14:16 ` Will Deacon
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=20140507212626.GD2844@laptop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=waiman.long@hp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox