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
  • Performance Analysis9
  • Accelerator Architectures6
  • SoC Architecture Tradeoffs9
  • Architecture Interview Prep14
    • Interview Method and Worked Scenarios
      • Architecture Whiteboard Framework
      • Scenario: Cache MPKI Storm
      • Scenario: NoC Deadlock Under Load
      • Scenario: Accelerator Starvation
      • Scenario: Coherency Traffic Storm
      • Validation, PPA and the Close
    • Architecture Interview Q&A Bank
Loading lesson

‹Interview Method and Worked Scenarios
  1. Topics
  2. Computer Architecture
  3. Architecture Interview Prep
  4. Interview Method and Worked Scenarios
  5. Architecture Whiteboard Framework

Computer Architecture · All levels

Architecture Whiteboard Framework

Five whiteboard steps from workload class to PMU validation, with sizing arithmetic.

On this page

    Name the workload and the target

    Each workload class stresses one structure. Streaming stresses bandwidth, pointer-chasing stresses the cache and TLB, sharing stresses coherence.

    State the target next: IPC or latency, plus power and area budgets. Assume a 3 GHz core with CPI_base 1.0 unless stated otherwise.

    Workload class

    Stresses

    First metric

    Branch-heavy control

    Fetch and predictor

    Mispredicts per kilo-instructions

    Pointer-chasing

    D-cache, TLB, LLC, DRAM

    MPKI by level plus TLB MPKI

    Streaming

    Prefetcher, bandwidth, NoC

    Bytes per cycle vs roof

    Sharing across cores

    Coherence and line size

    Invalidations per kilo-instructions

    Accelerator offload

    SRAM, DMA, launch path

    Active fraction of end-to-end time

    Draw the hierarchy and the coherence point

    Draw L1I, L1D, L2, L3 and main memory as one path. Mark the coherence point where all observers agree, usually the L3 or the interconnect directory.

    Label every arrow with what it carries: requests, responses, invalidations or writebacks. Deadlock and storm analysis both start from this sketch.

    Size with MPKI times penalty

    Each miss class adds MPKI times penalty over 1000 to CPI. The sum of the classes plus CPI_base is the predicted CPI.

    AMAT checks the hierarchy itself: hit time plus miss rate times miss penalty. Both formulas need stated example parameters, never vendor figures.

    Diagram
    CPI stall add = MPKI x penalty / 1000
      = 8 x 120 cycles / 1000 = 0.96 CPI added
    CPI = 1.0 + 0.96 = 1.96, IPC = 1 / 1.96 = 0.51
    
    AMAT = hit + miss_rate x (L2hit + L2miss_rate x DRAMpenalty)
      = 4 + 0.05 x (12 + 0.30 x 200)
      = 4 + 0.05 x 72 = 4 + 3.6 = 7.6 cycles
    Check yourself L2 MPKI doubles from 8 to 16 at 120 cycles penalty with CPI_base 1.0. What happens to IPC?

    CPI moves from 1.96 to 2.92, so IPC falls from 0.51 to 0.34. The added term is 8 x 120 / 1000 = 0.96 CPI.

    Validate with PMU events

    Name the counters that would confirm or refute the story. Instructions, cycles, misses per level and stall classes are the minimum set.

    One experiment per hypothesis, cheapest first. A counter reading beats a bigger cache as an answer.

    Claim

    Cheapest PMU check

    L2 capacity problem

    MPKI by level before and after a footprint change

    Conflict misses

    MPKI vs set-index histogram or way-miss distribution

    TLB reach problem

    TLB MPKI plus page-walk cycles

    NoC backpressure

    Queue occupancies plus per-class injection rates

    False sharing

    Invalidations per kilo-instructions plus line-bounce sampling

    Common pitfall

    Quoting peak bandwidth or a bigger cache as the answer skips the method. Interviewers fail answers that change hardware before reading counters.

    Interview

    Likely opener: size a hierarchy on the board.

    • Open with workload class plus IPC, latency, power and area targets.

    • Draw the levels and mark the coherence point before any number.

    • Close every size with MPKI times penalty and one PMU event that checks it.

    Check yourself The interviewer interrupts the sizing to ask how to check it in silicon. What is the answer?

    Name the PMU events: misses per level, stall classes and the one counter that separates the top two hypotheses. Then state the cheapest experiment first.

    Related topics

    • Performance method

    • Roofline and tuning

    Previous

    73 / 86

    Next: Scenario: Cache MPKI Storm

    Up next

    Up nextScenario: Cache MPKI Storm

    Sign in to save progress

    Practice this lessonReport an error

    See also

    • Scenario: NoC Deadlock Under Load
    • Scenario: Accelerator Starvation
    • Scenario: Coherency Traffic Storm