Kim Barrett

> > Multi-Reader Single-Writer mutex > > Sorry to bikeshed but such a thing is called a ReadWriteLock or a ReadersWriterLock or something similar - can we please use familiar...

HotSpot Mutex has a rank, used (in debug builds) to detect potential deadlock situations. These new mutexes don't have that feature, and don't interact with Mutex in that way. The...

What is the source of the algorithm being used here? Is there a correctness proof? How does it compare with, for example, Terekhov's algorithm?

> > How does it compare with, for example, Terekhov's algorithm? > > I'm not familiar with this algorithm, do you have a link? One place I found it. https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2007/n2406.html#shared_mutex...

> > For what it's worth, C++ Standard Library uses "mutex" to refer to an object that gets locked, and uses "lock" to refer to an RAII object that locks...

> > HotSpot Mutex has a rank, > > True, but I would put the read/write lock in the same basket as Semaphore, being completely independent of Mutex/Monitor. The onus...

> For some reason, I can't believe that we don't have this feature already in the vm, or at least, I was expecting this to be a simple wrapper over...

I don't expect this to be a popular opinion, but the more I think about it the less I like the direct use of PlatformMonitor here rather than using Monitor....

> Fix looks good as far as it goes (can't believe I didn't see what was going on here!) - but `os::signal` is still broken as it uses `sa_handler` instead...

> > > Fix looks good as far as it goes (can't believe I didn't see what was going on here!) - but `os::signal` is still broken as it uses...