80009b4c82
Add single-page (page_blk_size == kPageBlockSize == 128) paged instances for fp8 prefill_d128 (nmask + mask) and route page_blk_size==128 to them, so the canonical prefill shape exercises the kRebaseKSrd single-page addressing fast path (1 readfirstlane + 1 LDS block-table read + SRD rebase per tile). Two address-overhead optimizations bring the paged kernel to parity with (and slightly above) the contiguous baseline on b1 sq75600 hq=hk=5 d128 fp8: - Share the K/V per-lane scatter array. In the single-page rebase regime k_page_offsets == v_page_offsets bit-for-bit (same kv_cache strides, same fp8 DRAM distribution), so feed one loop-invariant array to both scatter- gather windows; the backend then coalesces the duplicated page_idx_ storage (nmask spills 5->1, mask 6->2). - Cross-stagger phys_page carry. K runs one tile ahead of V and shares the logical->physical page map, so V reuses the phys_page K already broadcast (R=2 tile-parity ring in SGPRs) instead of issuing its own block-table LDS read + readfirstlane. WG1 addr-phase stall drops 940 -> 64 cyc. Standalone (gfx950): paged 1810 -> ~1910 TFLOP/s noncausal (matches contiguous ~1905); causal 1463 -> 1592. 0% mismatch vs host reference. Contiguous path is unchanged -- all new code is gated on the paged single-page rebase flags. Co-authored-by: Cursor <cursoragent@cursor.com>
Composable Kernel Tile
concept
ck_tile provides a programming model with templated abstractions to enable users to implement performance-critical kernels for machine learning workloads. introduces following basic concepts to help users building your own operator
- tensor coordinate transformation, this is the core concept of layout/index transform abstraction in both compiler time and run time.
- tile-based programming model, including tile-level api and the concept of distributed tensor.
ck_tile is independently from the old ck, located under /include/ck_tile. You don't need to include anything from old CK, ck_tile has similiar (indeed almost the same) implementations for users to build operators. We will have a transition period to pull everything from old ck into ck_tile, stay tuned.
component
ck_tile is splitted into several componenets including core, host, ops/gemm, ops/fmha... each component you only need to include a single header (e.g #include "ck_tile/core.hpp", #include "ck_tile/ops/fmha.hpp") then you are able to use the function/structure inside (different from old ck)
[core]
ck_tile/core contains all the basic data structure and function to build the kernel, you can only include this header and build your own operators that utilizing all the basic building blocks introduced in ck.
core/container
- array, store runtime variables with fixed length (tensor index, register buffer, etc...)
- tuple, same as std::tuple, hold different type of data, and one of the solution to achieve multiple buffer.
- sequence, compile time integer sequence used to build various internal structures, or to describe tile size
- other convenient structure build on top of above 3
core/numeric
- gpu data type like
fp16_t,bf16_t,fp8_t... and the conversion between each other - constexpr integer similiar to std::integral_constant to be used as compile time integer.
- math functions and numeric utilities
core/algorithm
- coordinate transformation system, used to build tensor transform and compile time indexing. This is the core idea introduced in old
ckto describe how a tensor is build by several basic transform primitives likemerge/unmerge/embedetc... and how we indexing into a ND tensor that finally mapped to 1D memory offset.
core/tensor
- tensor descriptor, to describe how a ND tensor
- distributed tensor, describe the storage of this tensor, and the distribution of how a collection of threads collaborately work for this tensor.
- tile level API, including
load_tile,store_tile,shuffle_tile,slice_tile, etc...
[host]
ck_tile/host contains all the host side utilities to launch a kernel, create the device buffer, and some reference implementations. This can be used to create examples (like that under ck_tile example folder) and simple executable to invoke this kernel, so if you only need ck_tile to build your own device library then it's OK to not include this. Based on this, it is recommended to include the specific header you needed under this folder to avoid including unwanted headers (e.g, only include ck_tile/host/kernel_launch.hpp), unless you are writing a host executable.
[ops/gemm, ops/fmha, ops/reduce...]
our implementation of different device operators.
- warp, warp tile level operator
- block, block tile level operator
- pipeline, pipeline that can achieve a customized tile level mainloop (or epilogue). By switching different pipeline to the kernel template you can have different kind of pipeline optimizations.
- kernel, template interface for users to instantiate a particular kernel
[ops/epilogue]
epilogue part of our kernel. We may extend this epilogue part to let users to build their own cutomized epilogues.
[ref]
reference implementation of cpu or gpu. This folder is supposed to include a specific header on demand.
examples
currently we put all ck_tile related example under /example/ck_tile folder. Please check each example's subfolder.