rovarma

4 ms·

1. 1.▲
   by rovarma 7mo ago

   Leaving aside the vitriol... > The code that deadlocked was entirely written by Superluminal who grabbed a shared lock from a interrupt handler We don't "grab a shared lock". We call a kernel-provided eBPF helper function
2. 2.▲
   by rovarma 7mo ago

   Thanks! The new spinlock that the problem is in was introduced in kernel 5.15, which is relatively new, you need to be hooking context switches, and you need to be sampling at a high enough frequency that you hit the problem, and you ne
3. 3.▲
   by rovarma 7mo ago

   > Why not have context switches write to ringBuffer1 and sampling events write to ringBuffer2 (i.e. use different ringBuffers) That would work, but at the cost of doubling memory usage, since you then have two fixed-size ring buffers ins
4. 4.▲
   by rovarma 10mo ago

   Thanks! > In hindsight, making the sync point be paid for all users was a mistake, and an opt-in flag would have been the better option Yep. It was mentioned on the original patch’s mailing list discussion, but the cost was thought to be
5. 5.▲
   Superluminal – a new performance profiler for Windows(superluminal.eu)

   3 points by rovarma 8y ago|0 comments