[prev in list] [next in list] [prev in thread] [next in thread] 

List:       glibc-help
Subject:    pthread_once on ARM SMP
From:       jan () kloetzke ! net (Jan =?iso-8859-1?q?Kl=F6tzke?=)
Date:       2013-10-17 19:42:00
Message-ID: 201310172142.46009.jan () kloetzke ! net
[Download RAW message or body]

On Tuesday 15 October 2013, "Carlos O'Donell" <carlos@redhat.com> wrote:
> On 10/15/2013 02:49 PM, Jan Kl?tzke wrote:
> >> Remember that ARM does not have a weakly ordered memory
> >> model like Power, where it really is important to get all the
> >> barriers in the right places.
> > 
> > AFAIU ARMv7 (like Cortex A9 or A15) actually has a weakly ordered memory
> > model. The CPU might reorder reads and writes (in the absence of memory
> > barriers) and might do speculative reads too. I don't know the Power
> > memory model by heart but AFAIK the ARMv7 memory model is quite close.
> > [1]
> 
> I don't know if that's entirely true. I think that the ARMv7 architecture
> reference only mandates weakly ordered but in principle no implementation
> is weakly ordered. Therefore while the implementation of pthread_once is
> not strictly correct it still works. Eventually it will be incorrect for
> an implementation that is actually weakly ordered like Power.

I see. This makes sense.

> >> See the Power implementation for a "always correct" implementation.
> >> 
> >> Either way Torvald Riegel is rewriting all of the pthread_once
> >> implementations and unifying them:
> >> 
> >> https://sourceware.org/ml/libc-alpha/2013-10/msg00257.html
> >> 
> >> https://sourceware.org/ml/libc-alpha/2013-10/msg00416.html
> >> 
> >> https://sourceware.org/ml/libc-alpha/2013-10/msg00415.html
> > 
> > This looks good. The unified implementation is what I would have expected
> > on ARM too.
> 
> Please feel free to help in the review effort. We're going to try
> get all of the architectures onto the unified implmentation which is
> easier to review and audit.

The unified implementation looks good to me. This is (leaving the fork stuff 
aside) exactly what I would have expected in presence of a weakly ordered 
memory model.

Regards,
Jan


[prev in list] [next in list] [prev in thread] [next in thread]