Add chunked Qwen prefill with backend KV cache reuse - #549
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Extract reusable framework support for bounded, single-sequence Qwen prefill directly into the backend KV cache.
Additions
QwenCausalDecodeRuntime::prefill_embeddings_into_cache()to process embedding inputs in bounded blocks and continue token decoding from the same cache, without exporting and reimporting KV state through host memory.FastKVSetRowsModule::build_block()andQwenDecoderLayerModule::build_with_static_cache_block().TransformerKVCache::clear_on_backend()using the existing ggml tensor-memset API. It zeroes key/value tensors and resets position counters while retaining their allocations.Scope
The new prefill path is explicit opt-in and requires DirectSetRows with full last-token readback. Existing prefill entry points remain available. This PR contains no model integrations, model specifications, UI changes, or ggml modifications.