Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
sgemm-bi
Deterministic, batch-invariant CUDA GEMM engine with a full training triad — forward, weight gradient, and input gradient — in f32, bf16, and f16, plus an opt-in tensor-core tier.
Existing batch-invariant kernel collections cover inference only and trade
10–40% throughput for determinism. sgemm-bi covers the backward pass
too, and on tile-friendly shapes the tensor-core tier makes deterministic
training faster than a CUDA-core cuBLAS baseline.
Guarantees
- Run-to-run determinism — fixed reduction order in every kernel: no atomics, no data-dependent splits, no vendor-BLAS fallback. Same inputs → bit-identical outputs, including through CUDA Graph replay.
- Batch invariance — within a dispatch bucket, output row 0 is bit-identical regardless of the batch dimension M. The tensor-core forward is strictly batch-invariant across all M.
- Typed bit contract — bf16/f16 results are bit-identical to "upcast the inputs to f32, run the f32 tier, round-to-nearest-even downcast the output". Accumulation never happens in reduced precision; exactly one rounding is applied, at the output store.
Operations
| op | math | output |
|---|---|---|
forward |
Y[M,N] = X[M,K] @ W[K,N] + bias[N] |
typed / f32 |
backward_dw |
dW[K,N] += X^T[K,M] @ dY[M,N] |
f32 accumulate |
backward_dx |
dX[M,K] = dY[M,N] @ W^T[N,K] |
typed / f32 |
Each op exists in three tiers: *_f32 (the reference chain), typed
(bf16/f16, bit-equal to the f32 tier on upcast inputs), and *_tc
(tensor cores — a separate deterministic contract; mma.sync with f32
accumulators cannot bit-match a scalar FMA chain, but it is deterministic
and strictly batch-invariant).
The f32 and typed tiers cover every shape: a bucketed dispatcher
(Big / Slim / narrow / ultra-thin / GEMV / split-K/M/N with fixed-order
tree reduction) handles the common cases natively and the typed tier
falls back to "upcast → f32 kernel → downcast" — same bits by contract —
for the rest. The tensor-core tier covers both output dims ≥ 64 (two
bit-identical kernel families, 128×128 and 64×64 tiles, routed by shape)
and returns Error::Uncovered otherwise.
Performance (RTX 6000 Ada, bf16)
Tensor-core tier vs the scalar deterministic tier, GEMM level (forward; measured on this crate's bench suite):
| shape (M, K, N) | scalar | tensor cores | speedup |
|---|---|---|---|
| 2048, 768, 3072 | 290.9 µs | 83.4 µs | 3.5× |
| 4096, 1536, 3072 | 1123.0 µs | 353.5 µs | 3.2× |
| 2048, 768, 512 | 123.5 µs | 19.5 µs | 6.3× |
~116 TFLOPS bf16 at M2048 K768 N3072 (~32 % of Ada dense peak). dW and dX see similar gains (4.0–5.6× and 3.5–5.1× on the same shapes).
Against cuBLAS (measured in a host application using this engine for every training GEMM, same GPU, per optimizer step):
| dtype × tier | vs cuBLAS | model size |
|---|---|---|
| f32 scalar vs TF32 | 1.28–1.53× | full f32 precision vs truncated-mantissa TF32 |
| bf16/f16 scalar vs PEDANTIC | 1.09–1.37× | bit-contract, CUDA cores |
| bf16 TC vs PEDANTIC | 1.04× (d128) → 0.70× (d1536) | parity on small models, 16–30 % FASTER from d768 |
| f16 TC vs PEDANTIC | 1.19× (d128) → 0.76× (d1536) |
The cost of determinism is zero-to-negative on transformer-class shapes; the deterministic bf16 step at d1536 also beats the f32-TF32 baseline outright.
Documentation and examples
- Usage guide — recipes for all three interfaces, tier selection, CUDA Graph capture, determinism self-checks.
examples/deterministic_training.rs— full Rust triad with runtime determinism/invariance asserts (cargo run --release --example deterministic_training).examples/capi/smoke.c— the C ABI end to end.python/examples/train_deterministic.py— bit-identical PyTorch training, twice from one seed.- API reference: docs.rs/sgemm-bi; the Python
package ships typed stubs (
.pyi+py.typed), so IDE hover/completion documents the nativeEnginetoo.
Usage
use ;
let context = new.unwrap;
let stream = context.new_stream.unwrap;
let engine = new.unwrap;
// y/x/w are CUdeviceptr device allocations on `stream` (bf16 storage).
engine
.forward
.unwrap;
The engine binds to one stream; all calls enqueue and return. For CUDA
Graph capture, call presize_upcast_scratch before capturing so the
typed fallback never allocates inside (or after) a captured graph.
Requirements
- NVIDIA GPU,
sm_80+ for the bf16/f16 and tensor-core tiers (cp.async,ldmatrix, bf16mma.sync); the f32 tier runs on older architectures. - CUDA driver + NVRTC at run time. Kernels compile at engine construction
for the device's native architecture — no toolkit or
nvccneeded. - No cuBLAS: the library never links or calls a vendor BLAS.
Testing
Contract tests require a CUDA device:
Covered: f32 run-to-run bit identity; the typed bit contract swept across
~90 dispatch-gate boundary shapes (forward) plus backward shapes;
per-bucket batch invariance; tensor-core determinism, strict all-M
invariance, and accuracy vs the f32 reference. Benchmarks are #[ignore]d
(bench_tc_vs_scalar).
Lineage
The Big-tile kernels descend from siboehm's SGEMM warptiling work; smem padding follows salykova's sgemm.cu. The engine is extracted from the GEMM layer of mamba-rs, where it powers deterministic SSM training.
License
Dual-licensed under MIT or Apache-2.0.