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

  • How to Use This Course
  • Reading Path
  • Cache Coherency Glossary
  • The Shared Course Model
  • Cache Coherency Revision Sheet
  • Why Coherence Exists8
  • States and Protocols12
  • Transactions12
  • Races and Controller Design8
  • Progress and the Fabric16
  • Ordering and Synchronization12
  • Performance and Scalability12
  • Real Protocols12
  • SoC Integration12
    • LLC Data and Directory Policies
      • Inclusive, Exclusive and Non-Inclusive
      • Back-Invalidation
      • The LLC as Directory
      • Policy Trade-Offs
    • Devices and DMA
    • The Memory-Controller Boundary
  • Power, Clocking and Reliability12
  • Verification12
  • Debug and Bring-up12
  • Interview and Design Review17
  • Capstone: A Coherent Model Lab5
Loading lesson

‹SoC Integration
  1. Topics
  2. Cache Coherency
  3. SoC Integration
  4. LLC Data and Directory Policies

Part 9 · SoC Integration · All levels

LLC Data and Directory Policies

Define where a line lives across private caches and the LLC, and what that means for back-invalidation and directory lookups.

  • 4topics
  • 4lessons

The last-level cache, or LLC, adds data storage below the private caches. Its inclusion policy decides where a line goes on a miss, on a private eviction and on an LLC eviction, and whether an LLC tag lookup can double as the directory.

Note

Part 9 LLC model (extends the course model for this topic's examples only). The LLC sits at H. A PutM writes the LLC line, which becomes dirty relative to memory. Memory is written only when the LLC evicts a dirty line. This replaces the course's 'H writes memory' step for Part 9 LLC examples only. Eviction order stays PutM, then H writes the LLC line (assumed, H-internal), then Put-Ack. Snapshot tables add a column 'LLC: tag / value / dirty', for example 'X / 1 / dirty' or 'no tag'. The H directory column says where the entry lives: presence bits in the LLC tag (inclusive) or a separate snoop filter (exclusive, NINE). Private caches keep the course's MESI states. In these tables S{...} means the LLC line at H is current; DRAM may be older until the LLC evicts it.

Lesson

After it you can...

Inclusive, Exclusive and Non-Inclusive

Say where a line goes on a miss, a private eviction and an LLC eviction under each policy.

Back-Invalidation

Explain why an inclusive LLC eviction invalidates private copies, and what an inclusion victim is.

The LLC as Directory

Say when an LLC tag miss proves no private copy exists.

Policy Trade-Offs

Compare unique capacity, snoop filtering and bandwidth across the three policies.

Read after Part 7 directory capacity. Private MESI permissions follow the course model unchanged.

Check yourself Does an LLC tag hit prove its value is current?

No. A private M holder can hold newer data than the LLC. In the inclusive case the LLC tag carries presence bits that point H at that holder.

Related topics

  • Shared course model

  • Prerequisite: tracking capacity

PreviousNext: Inclusive, Exclusive and Non-Inclusive

Up next

Up nextInclusive, Exclusive and Non-Inclusive

Sign in to save progress

Practice this lessonReport an error

See also

  • Devices and DMA
  • The Memory-Controller Boundary