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
    • Read and Write-Permission Flows
      • Cold Read Miss
      • Read of a Shared Line
      • Write Miss and Ownership
      • Upgrade from Shared
    • Forwarding Versus Memory Sourcing
    • Writeback, Eviction and Cleaning
  • Races and Controller Design8
  • Progress and the Fabric16
  • Ordering and Synchronization12
  • Performance and Scalability12
  • Real Protocols12
  • SoC Integration12
  • Power, Clocking and Reliability12
  • Verification12
  • Debug and Bring-up12
  • Interview and Design Review17
  • Capstone: A Coherent Model Lab5
Loading lesson

‹Transactions
  1. Topics
  2. Cache Coherency
  3. Transactions
  4. Read and Write-Permission Flows

Part 3 · Transactions · All levels

Read and Write-Permission Flows

Separate cold reads, shared reads, write misses and upgrades by what the requester is missing: the value, the permission, or both.

  • 4topics
  • 4lessons

The question is not just which request was sent. Ask what the requester lacks: a usable value, a permission, or both. The four lessons below answer that question for the basic request types.

Lesson

After it you can...

Cold Read Miss

Say whether a lone reader gets S (MSI) or E (MESI) and why.

Read of a Shared Line

Explain why another reader need not revoke an existing reader.

Write Miss and Ownership

Acquire the value and exclusive permission from U or from a shared line.

Upgrade from Shared

Acquire permission without refilling bytes already present.

Read them in that order. Each example starts from its stated initial state or checkpoint. H handles one transaction for X at a time and keeps it pending until the final grant has been delivered, as the course model assumes.

Check yourself Which is a data miss: an I-to-M acquisition or an S-to-M upgrade?

The I-to-M acquisition lacks a usable value as well as write permission. The upgrade already has readable bytes; it lacks exclusivity. Both may wait on other agents.

Related topics

  • Shared course model

  • Prerequisite: state permissions

PreviousNext: Cold Read Miss

Up next

Up nextCold Read Miss

Sign in to save progress

Practice this lessonReport an error

See also

  • Forwarding Versus Memory Sourcing
  • Writeback, Eviction and Cleaning