Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for paged KV cache following the structure of KV-Compress, where cache blocks are paged out on a per-head basis.
In this case the cache shape becomes [num_blocks, block_size, d] (rather than [num_blocks, block_size, num_heads, d]) and the block table shape becomes [num_seqs, num_heads, max_blocks_per_seq] (rather than [num_seqs, max_blocks_per_seq]). Sequence lengths also need to be specified per-head, so that a (num_seqs * num_heads) or (num_seqs * num_heads + 1)-sized tensor is provided (depending on whether the sequence length or cumulative offsets are used).
I configured it to use the dimensionality of the block tables tensor to detect whether a KV-Compress cache is being used, assuming KV-Compress when dim > 2 and following the existing logic otherwise.