Write barrier
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.[1][2][3]
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.
See also
References
- ↑ "Chapter 16. Write Barriers". docs.fedoraproject.org. Retrieved 2014-01-24.
- ↑ "Documentation/block/barrier.txt". kernel/git/torvalds/linux.git - Linux kernel source tree. git.kernel.org. 2005-07-22. Retrieved 2014-01-24.
- ↑ "The end of block barriers". LWN.net. 2010-08-18. Retrieved 2014-01-24.
External links
- Barriers and journaling filesystems (LWN.net, May 21, 2008)
This article is issued from Wikipedia - version of the 11/30/2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.