Skip to content

optimze attn #19858

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

optimze attn #19858

wants to merge 2 commits into from

Conversation

momo609
Copy link

@momo609 momo609 commented Jun 19, 2025

Essential Elements of an Effective PR Description Checklist

  • The purpose of the PR, such as "Fix some issue (link existing issues this PR will resolve)".
  • The test plan, such as providing test command.
  • The test results, such as pasting the results comparison before and after, or e2e results
  • (Optional) The necessary documentation update, such as updating supported_models.md and examples for a new model.

Purpose

Test Plan

Test Result

(Optional) Documentation Update

wangxiaoxin (A) added 2 commits June 19, 2025 19:54
Copy link

👋 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 fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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 ready label to the PR or enable auto-merge.

🚀

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Summary of Changes

Hello @momo609, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request introduces a specialized tensor parallelism group dedicated to attention layers, aiming to optimize the distribution and processing of attention weights. By creating distinct linear layer implementations that leverage this new group, the change allows for more granular control over how attention mechanisms are sharded across devices, potentially leading to performance improvements or reduced memory footprint for large language models.

Highlights

  • Dedicated Attention Tensor Parallelism Group: Introduced a new _LM_HEAD_TP group and associated utility functions (get_lm_tp_group, get_lm_tensor_model_parallel_world_size, get_lm_tensor_model_parallel_rank) in vllm/distributed/parallel_state.py. This group is specifically initialized for 'lm_head_tp' and uses a message queue broadcaster, allowing for distinct tensor parallelism configurations for attention layers.
  • Specialized Attention Linear Layers: Added new linear layer classes, AttnColumnParallelLinear and AttnRowParallelLinear, and refactored AttnQKVParallelLinear in vllm/model_executor/layers/linear.py. These classes are designed to leverage the new _LM_HEAD_TP group for their tensor parallelism calculations, including determining shard sizes, ranks, and weight loading, enabling optimized sharding strategies for attention weights.
  • Qwen2 Model Integration: Updated the Qwen2Attention class in vllm/model_executor/models/qwen2.py to utilize the newly introduced AttnQKVParallelLinear and AttnRowParallelLinear classes for its QKV and output projections. This demonstrates the application of the attention-specific tensor parallelism for improved efficiency or memory usage.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@mergify mergify bot added the qwen Related to Qwen models label Jun 19, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request introduces a new tensor parallel group for the LM head, aiming to optimize attention mechanisms. The changes involve modifications to the parallel state and linear layers to accommodate this new group. The review focuses on providing suggestions for improved documentation and clarity within the code.

_LM_HEAD_TP: Optional[GroupCoordinator] = None

def get_lm_tp_group() -> GroupCoordinator:
assert _LM_HEAD_TP is not None, ("lm tensor model parallel group is not initialized")
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Consider adding a more descriptive error message that includes the specific group that failed to initialize.

Suggested change
assert _LM_HEAD_TP is not None, ("lm tensor model parallel group is not initialized")
assert _LM_HEAD_TP is not None, ("LM head tensor model parallel group is not initialized.")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
qwen Related to Qwen models
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant