[concurrency-interest] DirectByteBuffers and reachabilityFence

thurstonn thurston at nomagicsoftware.com
Fri Dec 11 15:58:42 EST 2015


It seems to me this is analogous to the "thread liveness/death" actions.

If thread A starts thread B, then all actions (thread A program order)
happen before, and therefore are visible to, thread B's running.

There is no *legal* execution possible where thread B doesn't 'see' any
prior (A po < ThreadB.start()) writes by thread A.

All of this can be stated without reference to an absolute temporal order,
although IMO, thinking about temporal order doesn't hurt anything.

And the converse is true for thread death
(Thread.join()/Thread.isAlive(false))



--
View this message in context: http://jsr166-concurrency.10961.n7.nabble.com/DirectByteBuffers-and-reachabilityFence-tp12935p13066.html
Sent from the JSR166 Concurrency mailing list archive at Nabble.com.


More information about the Concurrency-interest mailing list