7fc24c8c45
Two prefill_d128 changes on the unified-attention pingpong (checkpoint):
1. refresh_{k,v}_offsets: dedup the per-issue page-table lookup. With a
compile-time page_size the issue->page map is a pure compile-time
function in two provable regimes (page-divides-tile / tile-divides-
page), so phys_page is resolved once per distinct page instead of
once per issue -- collapsing to a single ds_read + readfirstlane at
page_size >= kPageBlockSize. Gated on kHasCePageSize; the runtime-
page-size scalar-promote and per-lane fallbacks stay byte-identical.
Measured fp8 prefill (ps=64), amir-shape sweep: +6.8% aggregate
(5-7%/shape, scaling with seqlen); B2 K-mem barrier straggler
-21..25%, total mean barrier stall -12%. Correctness verified
fp8 ps={32,64} and bf16 ps={16,32,64}.
(A cross-tile phys_page memo was prototyped and reverted: the Tier-2
LDS read is already cheap/hidden post-dedup, so the runtime guard +
loop-carried dep it needed was a net ~0.3% regression.)
2. Fork the FMHA CoreLoopScheduler into a UA-owned UAcoreLoopScheduler
and thread MOVE_FMHA_MASK_TO_COMPUTE through its sched_group_barrier
hints so the per-phase instruction-mix hint stays in lockstep with
mask code motion. With the macro at 0 the table is byte-identical to
the upstream FMHA scheduler (same hints, same codegen).
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.