Skip to content

Cnuas Datasheets

Product style datasheets for the Cnuas Virtual AI HPC Infrastructure platform and its components. Every component of the platform, hardware and software, has a datasheet here. Each one summarises features, functional specifications, interfaces, validation and integration information on a single reference sheet.

Emulated hardware

Cnuas is a 100% software-emulated virtual AI and HPC infrastructure. Every "device" below is a QEMU/userspace model, not physical silicon. Specification values describe the emulated device as presented to guest software (drivers, verbs, runtimes), so a virtual GPU or NIC behaves like the real part it models. Performance figures are functional/relative, not absolute hardware throughput.

Hardware datasheets

Document Datasheet Part Description PDF
DS-CNU-001 Cnuas Platform Platform Full data centre in a box: switches, adapters, accelerators, fabric, host requirements PDF
DS-CNU-002 CnuasSwitch cnuas-vswitchd 10 port soft top of rack RoCEv2 and InfiniBand switch with in switch subnet manager, runs as a host daemon PDF
DS-CNU-003 CnuasNIC cnuas-vnic RoCEv2 and native InfiniBand RDMA virtual adapter, guest resident PDF
DS-CNU-004 CnuasGPU cnuasgpu PCIe Gen5 x16 AI and ML accelerator with the CnuasIR instruction set and a CUDA style runtime, usable as a Soft GPU on the host or as a QEMU device PDF
DS-CNU-005 CnuasLink cnuasgpu-link-switchd Soft accelerator to accelerator fabric interconnect, runs as a host daemon PDF

Software datasheets

Document Datasheet Part Description PDF
DS-CNU-010 Cnuas Software Stack Software Map of the whole software stack and what is shipped against what is planned PDF
DS-CNU-011 CnuasRT libcnuasrt.so Accelerator runtime, CUDA Runtime style host API PDF
DS-CNU-012 CnuasDev libcnuasdev.so Device access library and the compute backend ABI PDF
DS-CNU-013 Kernel Modules cnuas_net.ko, cnuas_ib.ko, cnuasgpu.ko Guest drivers for the emulated network, RDMA and accelerator devices PDF
DS-CNU-014 Verbs Provider libcnuas-rdmav34.so rdma-core user space provider PDF
DS-CNU-020 Control Plane cnuas, cnuas-api Unified command line and REST API over every component PDF
DS-CNU-021 Cnuas Tools cnuas-tools Build, package, image, virtual machine, release and deployment tooling PDF
DS-CNU-022 Management Tools cnuassmi, cnuas-cli, cnuas-link-cli Per component operator clients and dashboards PDF
DS-CNU-030 Facility Twin cnuas-facility Campus digital twin, OpenUSD scene, power model and live telemetry PDF
DS-CNU-031 CnuasBMC cnuas-rackmond Rack and sled management controllers and the ORV3 power shelf PDF

Preview datasheets

These components are specified but carry no implementation. Each sheet opens with a notice saying so. They are published so that interfaces can be reviewed early and so the boundary between plan and product stays visible.

Document Datasheet Models Blocked on PDF
DS-CNU-015 CnuasCC nvcc CnuasIR instruction set freeze PDF
DS-CNU-016 CnuasIR PTX Instruction set freeze at version 1 PDF
DS-CNU-017 CnuasCCL NCCL CnuasCC PDF
DS-CNU-018 CnuasSHMEM NVSHMEM CnuasCC PDF
DS-CNU-019 Math Libraries cuBLAS, cuDNN, cuFFT, cuSPARSE, cuSOLVER CnuasCC PDF

Downloadable editions

Every datasheet is published in three forms from one Markdown source, so the website, the PDF and the text file cannot drift apart.

Format Purpose
Markdown This site
PDF Branded sheet for download and printing, linked from the tables above
Plain text Terminal reading, scripting and archival

The PDF column in each table links to pdf/<Name>_Datasheet.pdf on this site. Those files are copied in at build time from out/datasheets/, so a site built without running the datasheet build carries the Markdown edition only and the PDF links return not found.

Build the PDF and text editions locally:

python scripts/datasheet/build.py              # every datasheet
python scripts/datasheet/build.py CnuasGPU     # one datasheet
python scripts/datasheet/build.py --check      # validate document ids only

Output lands in out/datasheets/ with a manifest.json listing the document identity, revision and status of each sheet. The build needs pandoc and xelatex. Diagrams are rendered with mmdc when it is present, and fall back to a pointer to this site when it is not.

Verification and planning

For which features are proven by which tests, and whether those tests pass, see the Validation Matrix.

For feature availability and planned work across all components, see the Product Roadmap.

How to read these datasheets

Each datasheet follows a consistent layout:

  1. Identification, part, type, version and repository.
  2. Overview, one paragraph description and key features.
  3. Functional specifications, tabulated parameters.
  4. Interfaces, how the component is presented and controlled.
  5. Validation, which test proves which feature.
  6. Integration information, package name, versions, dependencies.
  7. Revision history.

Preview sheets replace the specification sections with the specified design and open with a notice that nothing is implemented.

These datasheets are summaries. For architecture, protocol walk-throughs, and implementation detail see the Design and Reference sections.