Mechanism to understand

Mechanism 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.

NoC topology, virtual channels, and QoS policies shape contention behavior under mixed traffic and determine predictable latency. Think of SoC integration as layered contracts: each layer can hide failures from the next unless boundaries are explicit and testable.

• Identify the boundary where this topic is enforced.

• Identify inputs each owner controls at that boundary.

• Identify the first measurable symptom when the contract breaks.

Layered view

SOC INTEGRATION STACK — NoC Topology & QoS

program contract (scope, milestones, ownership)
        |
        v
architecture contract (budgets, interfaces, assumptions)
        |
        v
implementation contract (rtl, timing, physical, package)
        |
        v
validation contract (bring-up, workload, signoff evidence)
        |
        v
release contract (manifest, waivers, tapeout decision)

Debug rule: always identify which contract layer broke first.

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

Layer responsibilities

SOC INTEGRATION LAYERS — NoC Topology & QoS

layer               owns                          failure mode
-----------------   ---------------------------   ------------------------
architecture        partition + contracts         impossible budgets
ip handoff          models + collateral           integration mismatch
fabric/clock/reset  global behavior               domain deadlock
physical/package    route + SI/PI + IO            late closure churn
signoff process     manifests + waivers           non-reproducible claims
program governance  owners + escalations          schedule collapse

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.

Mechanism deep dive

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