Choose a path
Read the contracts
Architecture, supported operators, admission gates, and deliberate exclusions.
Open the design →Connect an engine
Install the native wheel, preserve current streams, and enable narrow vLLM routes.
Open integration →Inspect the evidence
Separate operator, CUDA Graph, engine, parity, fallback, and rejected results.
Open the evidence index →Pick the next boundary
Follow the measured roadmap instead of implementing an unbounded operator checklist.
Open the roadmap →Check the qualified matrix
Separate source support, framework versions, H20 validation, and binary portability.
Open compatibility →Propose a measured operator
Name the engine call site, contract, baseline, and exit gates before a large implementation.
Open contributing →Validate the Rust core
The default workspace has no CUDA requirement. It checks dtype, shape, buffer, aliasing, and deterministic reference behavior first.
git clone https://github.com/feichai0017/loom-kernels.git
cd loom-kernels
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace --all-targets
cargo check --workspace --releaseContract correctness, accelerator correctness, named-baseline speed, framework dispatch, engine invocation, and serving benefit are six separate gates. Passing one never implies the next.
Workspace layers
| Layer | Responsibility |
|---|---|
| loom-kernels | Public contracts, capabilities, and deterministic CPU references. |
| loom-cuda | Safe stream/buffer ownership, checked dispatch, and benchmarks. |
| loom-cuda-sys | Internal CUDA launch ABI, compilation plumbing, and handwritten kernels. |
| loom-cuda-bridge | The only framework boundary into safe borrowed Rust dispatch. |
| python | Current-stream PyTorch operators and narrow vLLM integration. |
Qualify CUDA explicitly
CUDA_HOME=/usr/local/cuda-13.1 \
LOOM_CUDA_ARCHS=90 \
cargo bench -p loom-cuda --features cuda \
--bench add_rms_norm -- \
--dtype bf16 --rows 8 --hidden-size 4096Benchmarks check their GPU result against the CPU oracle before reporting CUDA-event latency. The complete result archive lives in the H20 evidence index.