[concurrency-interest] Suggestion: .hardGet() for atomic variables

Vitaly Davidovich vitalyd at gmail.com
Thu Jan 19 13:30:51 EST 2012


Volatile read does not allow subsequent operations to reorder with it - the
load must retire before subsequent reads/writes.  Check Doug Lea's compiler
cookbook if you're skeptical.

I don't see what reordering you're concerned about - can you give a simple
example?

Sent from my phone
On Jan 19, 2012 1:15 PM, "Raph Frank" <raphfrk at gmail.com> wrote:

> It doesn't have any happens before relationship with a later write.
>
> It is for optimistic read locks base on a sequence counter.  If the
> counter hasn't changed, then there is no guarantee that that
> happens-before the counter was incremented.
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20120119/6ef70b74/attachment.html>


More information about the Concurrency-interest mailing list