[concurrency-interest] AbstractQueuedSynchronizer

Martin Buchholz martinrb at google.com
Thu Sep 22 10:50:41 EDT 2016

On Thu, Sep 22, 2016 at 5:37 AM, Bobrowski, Maciej <
Maciej.Bobrowski at morganstanley.com> wrote:

> Thanks. So two questions:
> 1.       What does the set/unset blocker do?
Just for monitoring (identifying lock owner in stack traces), not
concurrency control.

> 2.       What is the token you are referring to? How does it relate to a
> latch, which is an entirely different object? In this case, there is no
> unpark called for that thread as it is not yet part of the wait queue AFAIK
When a thread can't make progress, it publishes a request to unpark in some
shared data structure, then parks.  If the unpark racily arrives before the
park, the park returns immediately.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20160922/aa691361/attachment.html>

More information about the Concurrency-interest mailing list