What problem does it solve?
It prevents common, CUDA-based misconceptions when writing GPU-targeted Mojo programs by mapping CUDA concepts to Mojo’s actual GPU programming model.
Core Features & Use Cases
- Not-CUDA concept mapping: replaces CUDA syntax and launch idioms with Mojo equivalents like
ctx.enqueue_function[...], barrier(), and Atomic.fetch_add.
- Correct kernel structure for GPUs: explains plain-function kernels,
TensorLayout-parameterized TileTensor usage, and mandatory comptime assert input.flat_rank == N when subscripting TileTensor.
- End-to-end GPU fundamentals: covers indexing (
global_idx, thread_idx, block_idx), shared memory allocation (stack_allocation with AddressSpace.SHARED), warp primitives, memory management via DeviceContext/DeviceBuffer, and host vs target GPU checks (has_* vs is_*).
Quick Start
Use the mojo-gpu-fundamentals skill while writing your Mojo GPU kernels so you replace CUDA-style syntax with the Mojo ctx.enqueue_function launch pattern and std.gpu/layout primitives.