Skip to content
DenseChip
Learn
PracticeCode labInterview

DenseChip

Navigate

Menu

LearnPracticeCode labInterview

Tools

All toolsSV editorCode repoResume
DenseChip

Practice, courses, and chip-design tools in one focused workspace.

LearnPracticeCode labInterviewToolsLearning paths

© 2026 DenseChip

AboutContactPrivacyTerms
Skip to lesson

Course contents

  • Architecture Metrics Reference
  • Workload Taxonomy for Architects
  • Architecture Glossary
  • Computer Architecture Cheatsheet
  • Pipeline Fundamentals14
  • Memory Hierarchy15
  • NoC and Interconnect Architecture6
  • Coherency and Memory Ordering9
    • Cache Coherence for the Architect
      • MESI States and the Single-Writer Invariant
      • Misses, Upgrades, and Evictions
      • Variants and Scaling: MOESI, MESIF, Snoop, Directory
      • ACE and CHI: An Honest Introduction
      • Sharing Costs and Coherence Triage
    • Memory Ordering Models
  • Performance Analysis9
  • Accelerator Architectures6
  • SoC Architecture Tradeoffs9
  • Architecture Interview Prep14
Loading lesson

‹Coherency and Memory Ordering
  1. Topics
  2. Computer Architecture
  3. Coherency and Memory Ordering
  4. Cache Coherence for the Architect

Computer Architecture · All levels

Cache Coherence for the Architect

How private caches stay coherent: MESI states, fabrics, ACE and CHI, and triage.

  • 5topics
  • 5lessons

Private caches of one address must agree on one value history. This topic builds that guarantee from the four MESI states up to fabric protocols and debug.

Four stable states and their moves.
Stable MESI edges only; transient states under races are covered in the lessons.

Lesson

What it covers

MESI states and the single-writer invariant

The four states, legal and forbidden edges, and why Exclusive exists.

Misses, upgrades, and evictions

BusRd, BusRdX, BusUpgr, acknowledgement counting, and a runnable model.

Variants and scaling

MOESI and MESIF, plus snoop broadcast against directory tracking.

ACE and CHI

An honest mapping-level introduction: CHI is not a newer ACE.

Sharing costs and coherence triage

Ping-pong, false sharing, timelines, triggers, and closure.

Check yourself Core 0 holds a line in M while core 1 holds the same line in S. Which invariant is broken, and what should the protocol have done?

Single-writer/multiple-reader is broken: M requires every other copy to be I. The writer must collect an invalidate acknowledgement from each sharer before entering M.

Interview

State all four MESI states with dirty/clean and exclusive/shared for each, then narrate one S-to-M upgrade with acknowledgement counting. Most follow-ups reduce to that narration.

PreviousNext: MESI States and the Single-Writer Invariant

Up next

Up nextMESI States and the Single-Writer Invariant

Sign in to save progress

Practice this lessonReport an error

See also

  • Memory Ordering Models