3 ms·
Actually this is exactly because someone in Windows used the plain old mutex. I'd call that "your granddad's lock". It's old, crotchety, unfair and shouldn't be
by AstralStorm 8y ago
Actually this is exactly because someone in Windows used the plain old mutex. I'd call that "your granddad's lock". It's old, crotchety, unfair and shouldn't be used in situations where any concurrency can be expected.
This despite the kernel having a nice RCU mechanism inside as well as waitfree queues.
- snaky 8y agoIf there was a spinlock, the problem stay. > the rule simply is that you MUST NOT release and immediately re-acquire the same spinlock on the same core, because as far as other cores are concerned, that's basically the same as never releasing it in the first place. https://yarchive.net/comp/linux/spinlocks.html https://yarchive.net/comp/linux/spinlocks.html Other mechanisms do exist of course.
- geezerjay 8y ago> I'd call that "your granddad's lock". It's old, crotchety, unfair and shouldn't be used in situations where any concurrency can be expected. What alternatives do you suggest?
- gpderetta 8y agoI guess: s/concurrency/contention/