Snoop & Cache Maintenance: Interview Drills

PROMPT
You see cache maintenance latency, invalidation count, stale data escapes on Snoop & Cache Maintenance. Walk through root cause and fix.

STRONG ANSWER
1. Names the layer and transaction identity.
2. Explains snoops and maintenance operations move cache lines between valid sharing states and clean stale visibility.
3. Requests line-state timeline, maintenance operation trace, software flush sequence.
4. Proposes one reduced sequence and one system regression.

WEAK ANSWER
Jumps to widening the interface, increasing FIFO depth, or blaming firmware without evidence.

CLEAN / INVALIDATE / FLUSH

CleanShared      : write dirty data out, keep line readable
Invalidate       : drop line, no writeback (data must be elsewhere)
CleanInvalidate  : write dirty data out, then drop line (flush)

Software ordering:
  write data -> clean to point of coherency -> start DMA
  DMA done   -> invalidate stale copies -> read fresh

ROOT-CAUSE TREE — Snoop & Cache Maintenance

cache maintenance latency, invalidation count, stale data escapes looks wrong
        |
   reproducible?
     /        \
   no          yes
   |            |
 flaky env   same first transaction every time?
 / seed         /            \
              yes             no
               |               |
        protocol rule     timing/reset/PVT
        or config bug     or load-dependent

COHERENCE TRAFFIC FLOW

RN issues coherent read
   -> HN looks up directory
   -> snoops to sharers
   -> data + state update returned

False sharing: different variables, same cache line -> coherence storm.

COHERENCY TRAFFIC STACK

data fetch        ████████
snoop responses   ██████████████
writebacks        ██████
maintenance ops   ████

High snoop stack with good IPC -> suspect line sharing before faster NoC.