[Lab] Lock Free Programming Lab
  • Introduction
  • Lock-free Programming
  • C11 Features on Concurrency
  • Lock-free vs Spin-lock
  • Lock-free Stack
  • ABA Problem
  • Memory Fence
  • Reference
Powered by GitBook
On this page

Was this helpful?

Reference

PreviousMemory Fence

Last updated 4 months ago

Was this helpful?

Introduction to look-free, wait free and the ABA problem:

ISO/IEC 9899:2011:

Toward a Better Use of C11 Atomics:

C++ concurrency in action:

C11 lock free stack:

Lock-Free Programming - Herb Sutter - CppCon 2014:

Hazard pointers: safe memory reclamation for lock-free objects:

It's "locking" if it's blocking

Do lock-free algorithms really perform better than their lock-full counterparts?

http://www.hergert.me/blog/2009/12/25/intro-to-lock-free-wait-free-and-aba.html
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1570.pdf
https://developers.redhat.com/blog/2016/01/14/toward-a-better-use-of-c11-atomics-part-1/
http://www.bogotobogo.com/cplusplus/files/CplusplusConcurrencyInAction_PracticalMultithreading.pdf
http://nullprogram.com/blog/2014/09/02/
https://github.com/CppCon/CppCon2014/blob/master/Presentations/Lock-Free%20Programming%20(or%2C%20Juggling%20Razor%20Blades)/Lock-Free%20Programming%20(or%2C%20Juggling%20Razor%20Blades)%20-%20Herb%20Sutter%20-%20CppCon%202014.pdf
http://ieeexplore.ieee.org/document/1291819/#full-text-section
https://yosefk.com/blog/its-locking-if-its-blocking.html
https://stackoverflow.com/questions/5680869/do-lock-free-algorithms-really-perform-better-than-their-lock-full-counterparts/