In operating systems, write barrier is a mechanism for enforcing a particular ordering in a sequence of writes to a storage system in a computer system. For example, a write barrier in a file system is a mechanism (program logic) that ensures that in-memory file system state is written out to persistent storage in the correct order.
In Garbage collection
A write barrier in a garbage collector is a fragment of code emitted by the compiler immediately before every store operation to ensure that (e.g.) generational invariants are maintained. A write barrier in a memory system, also known as a memory barrier, is a hardware-specific compiler intrinsic that ensures that all preceding memory operations "happen before" all subsequent ones.
In Computer storage
This section needs expansion. You can help by adding to it. (July 2016)
- "Chapter 16. Write Barriers". docs.fedoraproject.org. Retrieved 2014-01-24.
- Tejun Heo (2005-07-22). "I/O Barriers". kernel/git/torvalds/linux.git - Linux kernel source tree. git.kernel.org. Retrieved 2014-01-24.
- Jonathan Corbet (2010-08-18). "The end of block barriers". LWN.net. Retrieved 2014-01-24.
- Barriers and journaling filesystems (LWN.net, May 21, 2008)
|This software article is a stub. You can help Wikipedia by expanding it.|
|This computer-storage-related article is a stub. You can help Wikipedia by expanding it.|