News for hackers. Stuff that matters.
Re:Measuring mutexes, spinlocks and how bad the Linux schedu... by pixel_fcker on Tuesday December 31, 2019 @01:28PM (#21923189)
I think the answer, as always, is to measure on your own workloads. I’ve seen real-world production code get significant speed ups by switching to spinlocks from mutexes.

Very interesting post though. I’ve never considered the idle latency before.

There are no comments on this comment yet.