Add CPU-testable vLLM compaction boundary - #11
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.
Closes #7
Summary
2cf0a6915ce544dc493a0990f2ea38d81601128aVLLMCompactionPlannerDesign decision
vLLM's physical block table is shared across KV heads. Evicting whole blocks would force one retention mask across heads and silently change RandKV semantics. This boundary keeps selection head-specific and leaves block allocation plus PyTorch/CUDA copying to the runtime adapter.
Verification
ruff check .ruff format --check .mypy srcpytest -q— 25 passedpython -m build --no-isolationgit diff --checkLimitations
This does not patch or install vLLM and does not implement a CUDA kernel. It defines and tests the contract those pieces must consume.