ACE and CHI Protocol Introduction — Inputs & Outputs

Inputs required

• Protocol adaptation architecture document

• Interconnect channel capacity and credit configuration

• Traffic traces with barriers, atomics, and mixed cacheability

Outputs produced

• ACE-to-CHI semantic mapping matrix

• Protocol compatibility and corner-case risk list

• Migration verification plan with pass/fail criteria

Handoff owners

• Interconnect protocol architect

• Integration architect

• Performance validation lead

Production handoff contract

Treat ACE and CHI Protocol Introduction inputs as a signed contract between architecture, RTL, verification, software, performance, PD, and product owners. A 10+ year engineer blocks decisions when the contract is ambiguous instead of burning weeks on invalid comparisons.

HANDOFF MANIFEST
  workload_suite: <benchmarks, traces, production scenarios>
  model_tag: <spreadsheet / simulator / RTL / emulation / silicon tag>
  metric_contract: <IPC, MPKI, bandwidth, latency, power, area>
  architecture_assumptions: <cache sizes, line size, NoC topology, coherency mode>
  owner_of_truth: <architecture / performance / RTL / software owner>
  known_risks: <unmodeled effects, missing workloads, verification concerns>

Senior acceptance rules

1. Reject mismatched workload, model, PMU, or RTL tags before comparing metrics.

2. Record the owner for every assumption that is not locally provable.

3. Preserve enough metadata that another engineer can reproduce the experiment in six months.

Architecture input diagram

INPUT CONTRACT

workload suite ─┐
PMU / trace  ───┼──► architecture analysis ──► decision memo
RTL/model tag ──┤
PPA budgets  ───┤
SW contract  ───┘

Missing any one input changes the meaning of the metric.

Architecture deep dive

Coherency protocols trade traffic, latency, and verification complexity.

Concept diagram

MESI STATE SKETCH

        read miss          write
 Invalid ─────────► Shared ───────► Modified
    ▲                 │  ▲             │
    │ invalidate      │  │ downgrade   │ writeback
    └─────────────────┘  └─────────────┘

The interview bar is not naming states; it is explaining traffic and ordering.

Metric graph

COHERENCY TRAFFIC STACK

read shared      █████████████  42%
read exclusive   ███████        21%
invalidates      ██████████     31%
writebacks       █████          14%
snoop retries    ███            8%

False sharing often appears as invalidation spikes.

Metrics and artifacts

• coherency transaction rate

• snoop/filter efficiency

• ordering violation tests

• false sharing counters

Mini case study

Performance regression traced to false sharing on a counter array — coherency traffic exploded. Architecture fix: per-core counters + periodic merge, not faster NoC alone.

Debug branches

• If rare SW bug, run litmus and ordering tests before microarch changes.

• If traffic high, profile sharing patterns at cache-line granularity.

Senior review question

Ask: what single metric would prove this concept is working or failing on your workload?

Key takeaways

• Connect every architecture claim to a workload and measurable metric.

• State verification and PPA impact before proposing design changes.

Common pitfalls

• Feature-driven design without MPKI/IPC/bandwidth evidence.

• Ignoring coherency and NoC traffic in cache and accelerator sizing.

Study notes

Re-read this topic with one concrete workload.