DenseChip

SoC Integration · All levels

NoC Topology & QoS: Step-by-Step Walkthrough

Step-by-Step Walkthrough for NoC Topology & QoS.

Step-by-step analysis walkthrough

Use when you own NoC Topology & QoS in a top-level integration review.

  1. Open latest integration baseline and manifest.

  2. Inspect failing metric by domain.

  3. Trace first failing contract boundary.

  4. Collect artifacts and assign single-thread owner.

  5. Define minimal proof experiment.

  6. Apply smallest reversible fix.

  7. Run focused check then full regression.

  8. Update dashboard and governance log.

  9. Decide: close, waive with expiry, or escalate.

  10. Publish final review memo.

Artifacts to collect

  • NoC topology map, VC utilization report, QoS policy table

  • baseline manifest

  • owner matrix

  • regression summary

  • risk memo

Decision memo template

diagram
SOC DECISION MEMO — NoC Topology & QoS
baseline:
metric:
root cause:
fix:
residual risk:
owners: NoC architect, performance owner, integration owner

Reference visuals

NoC topology with QoS classes

diagram
NOC TOPOLOGY

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

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

SoC deep dive

Fabric correctness and contention behavior must be proven together.

Concept diagram

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

Metric graph

diagram
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

Practice this lesson