-
-
Notifications
You must be signed in to change notification settings - Fork 9.8k
[V1] Fix local chunked attention always disabled #21419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: Yong Hoon Shin <[email protected]>
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This PR correctly fixes a bug where self.use_irope
was always being set to False
due to being overwritten. While the fix is logically sound for the stated problem, I've identified a potential critical issue with the underlying logic of using pop
vs get
for V1 and V0 code paths. This could be a latent bug related to how quantization parameters are handled. My review includes a suggestion to make the behavior consistent and likely more correct.
@vladmihailescu has imported this pull request. If you are a Meta employee, you can view this in D78782520. |
Importing this diff internally for an A/B perf test for Llama4 Maverick on H100 |
Good catch @sarckk! Are we missing some unit test coverage for local attention? I would expect some test failure when we disable things. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch!! I appreciate you fixing this! Thanks for the contribution
Signed-off-by: Yong Hoon Shin <[email protected]> Signed-off-by: avigny <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]> Signed-off-by: shuw <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]> Signed-off-by: x22x22 <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]> Signed-off-by: Jinzhen Lin <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]> Signed-off-by: Paul Pak <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]> Signed-off-by: Boyuan Feng <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]> Signed-off-by: Diego-Castan <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]>
Signed-off-by: Yong Hoon Shin <[email protected]>
Essential Elements of an Effective PR Description Checklist
supported_models.md
andexamples
for a new model.Purpose
#21188 and #19351 made similar and conflicting changes around
self.use_irope
in Attention layer, causingself.use_irope
to always beFalse
in V1:We should not pop
use_irope
in V0 as attention backends still expectuse_irope
as an arg (example)Test Plan
ruler niah_multikey_2
Test Result
baseline:
This PR:
cc: @luccafong @minosfuture @houseroad @yeqcharlotte