Advanced Topic 46 of 51 Computer Architecture & Logic
Memory Consistency Models
Rules on the apparent order of memory operations across cores.
How it works
A memory consistency model defines the order in which memory reads and writes by different threads may appear to each other. Sequential consistency requires a single global order matching each program's order, while weaker models such as x86 total store order and ARM or RISC-V relaxed models let hardware reorder operations for speed using store buffers and caching. Fences and atomic operations with acquire and release semantics restore ordering where needed.
Step-by-step walkthrough
- Core 1 writes x = 1 then y = 1.
- Core 2 reads y and sees 1.
- With a weak model it may still read x = 0.
- Store buffers and reordering make writes visible in different orders.
- Fences or atomic operations enforce the order the program needs.
Where it is used
Writing lock-free algorithms, implementing locks and atomics, designing language memory models in C++, Java and Rust and reasoning about concurrent code depend on the consistency model.
Common pitfall
Code that works on x86 may break on ARM because of weaker ordering. Data races without synchronization give undefined or surprising results. Compilers also reorder operations. Use the language's atomics and locks rather than hand-rolled flags, and test on weak-memory hardware.
Where it fits in the course
Memory Consistency Models is topic 46 of 51 in Computer Architecture & Logic, rated Advanced. It follows RAID. The next topic is Microarchitecture Side Channels.
Practice and explore
- Open the interactive lesson, with a mini quiz.
- Take the Computer Architecture & Logic quiz.
How to study this topic
- Read the explanation above and restate the definition in your own words.
- Open the interactive lesson and answer its mini quiz.
- Read the common pitfall, then write a short example that avoids it.
- Check your understanding in the Computer Architecture & Logic quiz, and revisit the topic if you miss a question.
Frequently asked questions
What is Memory Consistency Models?
Where do people use Memory Consistency Models?
What is the most common mistake with Memory Consistency Models?
What should I learn before this topic?
How can I practice it?
Is Memory Consistency Models hard to learn?
How long does it take to learn Memory Consistency Models?
Which topics are related to Memory Consistency Models?
What should I study after Memory Consistency Models?
Related topics
- RAID (Computer Architecture & Logic)
- Microarchitecture Side Channels (Computer Architecture & Logic)
- Storage Devices (Computer Architecture & Logic)
- FPGA (Computer Architecture & Logic)
- Consistency Models (Distributed Systems & Cloud)
- Memory Models in Languages (Concurrency & Parallelism)
- Color Models (Graphics, Vision & Media)