Memory Barrier

Memory barrier, also known as membar or memory fence or fence instruction, is a type of barrier and a class of instruction which causes a central processing unit (CPU) or compiler to enforce an ordering constraint on memory operations issued before and after the barrier instruction.

CPUs employ performance optimizations that can result in out-of-order execution. The reordering of memory operations (loads and stores) normally goes unnoticed within a single thread of execution, but causes unpredictable behaviour in concurrent programs and device drivers unless carefully controlled. The exact nature of an ordering constraint is hardware dependent, and defined by the architecture's memory ordering model. Some architectures provide multiple barriers for enforcing different ordering constraints.

Memory barriers are typically used when implementing low-level machine code that operates on memory shared by multiple devices. Such code includes synchronization primitives and lock-free data structures on multiprocessor systems, and device drivers that communicate with computer hardware.

Read more about Memory Barrier:  An Illustrative Example, Low-level Architecture-specific Primitives, Multithreaded Programming and Memory Visibility, Out-of-order Execution Versus Compiler Reordering Optimizations

Famous quotes containing the words memory and/or barrier:

    His memory is like wares at the auction—going, going, and anon it will be gone.
    Herman Melville (1819–1891)

    ... social evils are dangerously contagious. The fixed policy of persecution and injustice against a class of women who are weak and defenseless will be necessarily hurtful to the cause of all women.
    —Fannie Barrier Williams (1855–1944)