SoC Integration · All levels

NoC Topology & QoS: Inputs & Outputs

Inputs & Outputs for NoC Topology & QoS.

Inputs and outputs contract

Inputs & Outputs 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.

Treat these as a signed integration contract. Ambiguity here causes multi-team debug loops where everyone is right inside their own assumptions.

diagram

INPUTS
  - baseline manifest (versions + hashes)
  - interface/budget contract revision
  - mode assumptions (functional/test/low-power)
  - owner accountability map

OUTPUTS
  - measurable closure deltas
  - owner-approved fix proposal
  - regression evidence package
  - risk/waiver disposition

Integration sequence

diagram

SOC INTEGRATION FLOW — NoC Topology & QoS

requirements + budgets
        |
        v
IP handoff + collateral check
        |
        v
integration build + bring-up smoke
        |
        v
cross-domain signoff evidence
        |
        v
tapeout readiness decision

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

Ownership map

diagram

OWNERSHIP MAP — NoC Topology & QoS

artifact             owner
-----------------    -----------------
primary owner     NoC architect
co-owner          performance owner
review owner      integration owner

No top-level issue should remain ownerless beyond one review cycle.

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