Introduction to Lock-free Programming - Tony van Eerd

This talk will cover some of the problems of lock-free, some of the reasons why these problems exist (what is the CPU doing), and, honestly, try to make you afraid to write lock free code, because it is too easy to get wrong.
As examples, parts of simple lock-free structures will be shown.

NDC Conferences

[QuasiUnlimited]

Great talk! The GOTO killed me at 16:00 but it make total sense, like you said in lock-free world forget everything you know 😀

[brenogi]

Great talk!
Btw, there is a typo on the "push" slide. It says "count.compare_exchange". I believe it should be "stack.head.compare_exchange", right?

[timh.]

Kinda sad that he spends nearly an hour explaining this technique and concludes with "you should only use this as a last resort, and even then it might not help".

[Muskar]

Why use RAII in lock-free programming?! That seems like completely unnecessary overhead when you're trying to squeeze out performance. Instead you should malloc a huge page at startup and manage it yourself in an arena/pool or a circular buffer.

[Maric]

i like my GIL actually
everything that needs to be fast can be outsourced ... which brings me here
but the fewer times that i have to actually do complex and cool work, the fewer bugs i can produce

[meyou]

rofl - thats was super funny @ 36:00 ish