Files
kernbench2/docs/adr/ADR-0003-target-system-hierarchy.md
T
ywkang fc6abbc8ee Add CHANGES.md, README, update SPEC/ADRs for release 2
- CHANGES.md: detailed changelog for release 1 and 2
- README.md: full project docs with install, probe, run, test usage
- SPEC.md: add ADR-0014~0017 references, update R7 for pcie_ep endpoint
- ADR-0003: update NOC description to reference ADR-0017
- ADR-0004: add HBM efficiency factor (0.8) to BW guarantee contract
- ADR-0014: status Proposed -> Accepted
- ADR-0015: update D4 to M_CPU bypass for Memory R/W, add ADR-0016/0017 links
- ADR-0016 (new): IOChiplet NOC and memory data path
- ADR-0017 (new): Cube NOC 2D mesh architecture
- Fix MD lint warnings (unfenced code blocks) across all docs

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-19 01:43:15 -07:00

2.3 KiB
Raw Blame History

ADR-0003: Target System Hierarchy & Modeling Scope

Status

Accepted

Context

We need a system-level simulator to evaluate LLM kernel performance on our AI Accelerator platform. The platform is organized as a compute tray containing multiple identical SIPs connected via PCIe or UAL through switching fabrics, with a host CPU issuing commands/kernels.

Decision

We model the system hierarchy explicitly:

D1. Tray-level

  • A compute tray contains:
    • Host CPU (issues requests / coordinates runtime & data placement)
    • Multiple identical SIPs (accelerators)
    • Interconnect fabric between SIPs (PCIe and/or UAL via switches)

D2. SIP-level

  • A SIP is a multi-die package composed of:
    • Multiple CUBEs (HBM die + compute PEs + UCIe)
    • One or more IO chiplets (host/SIP interfaces)
  • IO chiplets:
    • provide interfaces: PCIe-EP, IO_CPU, optionally UAL-EP
    • can be multiple per SIP
    • placement constrained to SIP shoreline (top/bottom/left/right); each shoreline may host 12 IO chiplets

D3. CUBE-level

  • A CUBE contains:
    • HBM + memory controller (HBM_CTRL)
    • XBAR (top/bottom): HBM pseudo-channel crossbar, PE's dedicated path to HBM
    • Bridge (left/right): connects XBAR.top ↔ XBAR.bottom for cross-half HBM access
    • NOC: 2D mesh router grid spanning the entire cube with XY routing and per-segment contention modeling; carries all intra-cube traffic including PE DMA to xbar (HBM), inter-cube (UCIe), command (M_CPU↔PE_CPU), and shared SRAM access. See ADR-0017 for full NOC architecture.
    • Shared SRAM: cube-level shared memory accessible by all PEs via NOC
    • management/control CPU (M_CPU) coordinating PE command distribution and completion aggregation
    • multiple PEs
    • up to 4 UCIe endpoints (N/E/W/S) for CUBE↔CUBE and CUBE↔IO connectivity

D4. PE-level

  • A PE can execute one kernel instance
  • PE contains internal control + accelerators (modeled at PE view granularity):
    • PE_CPU, command handler, PE_TCM, DMA/GEMM/MATH engines, internal queues

Consequences

  • The simulator supports abstraction by “views”:
    • SIP view hides PE internals
    • CUBE view treats each PE as a single block
    • PE view expands PE internals
  • Topology remains parameterized; sizes/counts/links come from configuration.
  • SPEC R3/R5
  • ADR-0005 (diagram views)
  • ADR-0017 (cube NOC 2D mesh architecture)