News for hackers. Stuff that matters.
Re:Mutexes are faster than Spinlocks by rumanator on Saturday January 04, 2020 @01:56PM (#21956631)
> and nothing else is supposed to run on those cores

That's quite the corner case.

Re:Mutexes are faster than Spinlocks by titzer on Saturday January 04, 2020 @04:20PM (#21957656)
This is exactly the situation for a well-balanced parallel work queue. You want to start as many threads as there are cores and run them full tilt pulling work off the queue until it is empty. If you're running a large scale cluster that is dedicated to a particular task (e.g. like servicing a special kind of query, or encoding videos, rendering, etc), this is very common, or even a parallel Photoshop filter.
Re:Mutexes are faster than Spinlocks by rumanator on Saturday January 04, 2020 @04:26PM (#21957698)
> This is exactly the situation for a well-balanced parallel work queue.

What if your work queues are running on a multitasking operating system that runs services? And what about a hypervisor?

Re:Mutexes are faster than Spinlocks by johncolanduoni on Saturday January 04, 2020 @05:47PM (#21958167)
For this technique you generally dedicate some core(s) to those miscellaneous threads and flag the rest as unscheduable unless a thread is specifically assigned to them.

If you’re not sharing cores between VMs it’s typical to do the same at the hypervisor layer.

Re:Mutexes are faster than Spinlocks by shaklee3 on Saturday January 04, 2020 @11:17PM (#21959602)
This is the normal use case for any DPDK software. I think anyone involved in HPC or high-speed networking knows that this is pretty common.
Re:Mutexes are faster than Spinlocks by gpderetta on Saturday January 04, 2020 @06:14PM (#21958323)
Yes, in practice you have to dedicate the whole machine for a specific application, but the one thread per isolated core is a proven one for high performance/low latency applications.