Re:On mutex performance and WTF::Lock
by eridius on Sunday April 02, 2017 @04:11PM
(#14018800)
Thread starvation is still very much a thing on a lot of devices. macOS and iOS even have a Quality Of Service implementation in the kernel specifically to ensure that high-priority threads get to run when they'd otherwise be starved, and this can lead to low-priority threads being suspended for many seconds at a time under high workload. In fact, it's now really dangerous to use a regular spinlock on iOS and macOS because you can get into a priority inversion livelock if threads from different QoS levels are contending the same lock. The Obj-C runtime was seeing delays of tens of seconds in some cases when using spinlocks, so it now uses a private "os_lock" which is a spinlock that uses SPI to "donate" the QoS of the waiting thread to the one that holds the spinlock.
[ Parent
| on HN ]
Re:On mutex performance and WTF::Lock
by LeoNatan25 on Sunday April 02, 2017 @06:14PM
(#14019354)
As of iOS 10 and macOS 10.12, it is no longer private: `os_unfair_lock`.
Oh good! I'll have to do some research at some point to find out if this is literally the same thing as the os_lock that the Obj-C runtime uses, but either way, I'm glad it's available now.
Re:On mutex performance and WTF::Lock
by LeoNatan25 on Monday April 03, 2017 @03:56AM
(#14021236)
It uses the same private API (or at least, what you described in your previous post).