With --prefix-match-unit below the block size, a follow-up turn that resumes at a partial tail (mid-block) never hashes a block-boundary GDN state. Under retention interval 0 the only boundary kept is the replay boundary, which lies below the resume point. The request's own tail is published on its running block and moved into a CoW block by the next chunk, and the scheduler releases both copy endpoints once the copy has run. That block then sat at ref 0 in the free queue for the rest of the request, ahead of its attention blocks, and concurrent prefills popped it. The hybrid hit is the shortest group's, so the next turn resumed at 0. Under a long-context multi-turn agent load, 7 of 61 follow-ups at unit 64 (6 at 256/512/1024) came back with cached_tokens 0 on 80-100K prompts whose whole attention prefix was still cached. Every one followed a partial-tail resume, none followed a block-aligned one, and unit 4096 never missed. The existing retention (VLLM_E2_MAMBA_RETAIN_CHECKPOINT) only held hashed blocks retired from the table, so it never covered that copy. Now, under the same switch: - The running-request CoW branch holds the moved tail block in _retained_checkpoints with a ref of its own; the copy retention pair is unchanged. The new-request branch holds the hit source after _apply_cow for the same reason: a request that stops before its own tail still leaves the state it resumed from. - _retained_checkpoints is keyed by block_hash_num_tokens instead of block index, so a sub-block tail key orders correctly against full block states; _retire_state_blocks uses the same key. The newest position supersedes and releases the older one, so a request still holds at most one block per group. - When a producer moves its tail hashes into its CoW block, another request holding that source (a sibling that resumed at the tail while it was the producer's live block) follows the hashes to the copy. - Admission reserves one extra block per Mamba group for a partial-tail hit: the held source and the moved tail coexist at the tail step. The hold is released on every free path (finish, abort, preemption, deferred pop_blocks_for_free) by the coordinator, last, after the request's attention blocks, as before. When the hold is active (switch on, hash unit below the Mamba block) MambaManager logs one startup line saying so, with the hash unit and block size. Tests (CPU): a replay of the miss that fails on v2.5.0 with the retention switch on (next-turn hit 0 instead of the tail) and passes here; the structural variant; admission accounting; no-leak checks for a request freed with its copy still queued, in both release orders; and the moved-hash follow. The retention suite's one block-index assertion now reads the token position. Co-Authored-By: Hinata <hinata@idihore.id> Signed-off-by: MOVZX <movzx@yahoo.com>
Easy, fast, and cheap LLM serving for everyone
| Documentation | Blog | Paper | Twitter/X | User Forum | Developer Slack |
🔥 We have built a vLLM website to help you get started with vLLM. Please visit vllm.ai to learn more. For events, please visit vllm.ai/events to join us.
About
vLLM is a fast and easy-to-use library for LLM inference and serving.
Originally developed in the Sky Computing Lab at UC Berkeley, vLLM has grown into one of the most active open-source AI projects built and maintained by a diverse community of many dozens of academic institutions and companies from over 2000 contributors.
vLLM is fast with:
- State-of-the-art serving throughput
- Efficient management of attention key and value memory with PagedAttention
- Continuous batching of incoming requests, chunked prefill, prefix caching
- Fast and flexible model execution with piecewise and full CUDA/HIP graphs
- Quantization: FP8, MXFP8/MXFP4, NVFP4, INT8, INT4, GPTQ/AWQ, GGUF, compressed-tensors, ModelOpt, TorchAO, and more
- Optimized attention kernels including FlashAttention, FlashInfer, TRTLLM-GEN, FlashMLA, and Triton
- Optimized GEMM/MoE kernels for various precisions using CUTLASS, TRTLLM-GEN, CuTeDSL
- Speculative decoding including n-gram, suffix, EAGLE, DFlash
- Automatic kernel generation and graph-level transformations using torch.compile
- Disaggregated prefill, decode, and encode
vLLM is flexible and easy to use with:
- Seamless integration with popular Hugging Face models
- High-throughput serving with various decoding algorithms, including parallel sampling, beam search, and more
- Tensor, pipeline, data, expert, and context parallelism for distributed inference
- Streaming outputs
- Generation of structured outputs using xgrammar or guidance
- Tool calling and reasoning parsers
- OpenAI-compatible API server, plus Anthropic Messages API and gRPC support
- Efficient multi-LoRA support for dense and MoE layers
- Support for NVIDIA GPUs, AMD GPUs, Intel GPUs, and x86/ARM/PowerPC CPUs. Additionally, diverse hardware plugins such as Google TPUs, Intel Gaudi, IBM Spyre, Huawei Ascend, Rebellions NPU, Apple Silicon, MetaX GPU, and more.
vLLM seamlessly supports 200+ model architectures on Hugging Face, including:
- Decoder-only LLMs (e.g., Llama, Qwen, Gemma)
- Mixture-of-Expert LLMs (e.g., Mixtral, DeepSeek-V3, Qwen-MoE, GPT-OSS)
- Hybrid attention and state-space models (e.g., Mamba, Qwen3.5)
- Multi-modal models (e.g., LLaVA, Qwen-VL, Pixtral)
- Embedding and retrieval models (e.g., E5-Mistral, GTE, ColBERT)
- Reward and classification models (e.g., Qwen-Math)
Find the full list of supported models here.
Getting Started
Install vLLM with uv (recommended) or pip:
uv pip install vllm
Or build from source for development.
Visit our documentation to learn more.
Contributing
We welcome and value any contributions and collaborations. Please check out Contributing to vLLM for how to get involved.
Citation
If you use vLLM for your research, please cite our paper:
@inproceedings{kwon2023efficient,
title={Efficient Memory Management for Large Language Model Serving with PagedAttention},
author={Woosuk Kwon and Zhuohan Li and Siyuan Zhuang and Ying Sheng and Lianmin Zheng and Cody Hao Yu and Joseph E. Gonzalez and Hao Zhang and Ion Stoica},
booktitle={Proceedings of the ACM SIGOPS 29th Symposium on Operating Systems Principles},
year={2023}
}
Contact Us
- For technical questions and feature requests, please use GitHub Issues
- For discussing with fellow users, please use the vLLM Forum
- For coordinating contributions and development, please use Slack
- For security disclosures, please use GitHub's Security Advisories feature
- For collaborations and partnerships, please contact us at collaboration@vllm.ai
Media Kit
- If you wish to use vLLM's logo, please refer to our media kit repo
