NoC Topology & QoS: Interview Drills

Interview drills

Interview Drills for NoC Topology & QoS focuses on fabric latency p99, starvation incidents, QoS target hit-rate. The goal is to map symptoms to boundary contracts, owner actions, and regression-proof closure.

PROMPT
You observe fabric latency p99, starvation incidents, QoS target hit-rate in NoC Topology & QoS. Explain root cause and closure plan.

STRONG ANSWER
1. Names baseline manifest and failing boundary.
2. Explains NoC topology, virtual channels, and QoS policies shape contention behavior under mixed traffic and determine predictable latency.
3. Requests NoC topology map, VC utilization report, QoS policy table.
4. Proposes minimal reversible fix + full regression scope.

WEAK ANSWER
Suggests broad optimizations or owner blame without baseline and artifact evidence.

Diagram to draw on whiteboard

NoC topology with QoS classes

NOC TOPOLOGY

CPU ---DMA ----> [NoC routers + VCs] ---> DDR / IO / accelerators
GPU ---/

QoS class A: latency-sensitive
QoS class B: throughput-sensitive

Root-cause tree to narrate

ROOT-CAUSE TREE — NoC Topology & QoS

fabric latency p99, starvation incidents, QoS target hit-rate regressed
         |
   same baseline manifest?
      /           \
    no             yes
    |               |
version/collateral  real integration
mismatch            contract break
 /       \            |
inputs    env      isolate domain
drift     drift    and first failure

SoC deep dive

Fabric correctness and contention behavior must be proven together.

Concept diagram

FABRIC FLOW
masters -> routers/VCs -> slaves + memory

Metric graph

LATENCY TAIL
p50 ███
p95 ██████
p99 ██████████

Reports and artifacts

• NoC contention heatmap

• ordering violation report

• QoS fairness summary

• protocol trace

Mini case study

Bandwidth looked fine at average load, but p99 tail violated SLA due to arbitration starvation.

Debug branches

• Isolate traffic class

• Check ordering assumptions

• Audit arbitration policy

Senior review question

Ask: what baseline, owner, and artifact prove this topic is truly closed?

Key takeaways

• State baseline manifest and owner with every closure metric.

• Run cross-domain regression after every top-level fix.

Common pitfalls

• Comparing results across different manifests.

• Unowned issues slipping through review cycles.

• Waiving risks without expiry and validation plan.

Principal SoC review addendum

NoC topology, virtual channels, and QoS policies shape contention behavior under mixed traffic and determine predictable latency.

Metric: fabric latency p99, starvation incidents, QoS target hit-rate