Memory barriers: Difference between revisions

Memory barriers (view source)

198 bytes added , 5 years ago

Fixed blog links

[unchecked revision]

Anonymous user

Revision as of 20:49, 1 February 2009 (view source) osdev>Berkus (New page: Memory barriers ensure ordering of load/store commands. Usually CPUs and compilers reorder these instructions for more efficient execution. Lock-free algorithms often require that perceiv...)		Latest revision as of 04:05, 22 August 2018 (view source) osdev>Nullplan (Fixed blog links)
(3 intermediate revisions by 2 users not shown)
Line 7: Memory Ordering in Modern Microprocesors, [http://www.linuxjournal.com/article/8211 Part 1] and [http://www.linuxjournal.com/article/8212 Part 2] Ridiculous Fish's [http://ridiculousfish.com/blog/~~archives/2007/02/17~~posts/barrier/.html controversial article]] about using and abusing memory barriers. (and [http://www.thinkingparallel.com/2007/02/19/please-dont-rely-on-memory-barriers-for-synchronization/ some bashing of this article] just for a different POV) [http://www.gelato.unsw.edu.au/lxr/source/Documentation/memory-barriers.txt Documentation with explanations on what memory barriers are used in linux kernel and why.] {{stub}} [[Category:Synchronization]]