Skip to content

[ROCm] Enable DeepEP ROCm as all2allbackend for AMD GPUs. #34692

Draft
lcskrishna wants to merge 3 commits intovllm-project:mainfrom
ROCm:rocm-deepep
Draft

[ROCm] Enable DeepEP ROCm as all2allbackend for AMD GPUs. #34692
lcskrishna wants to merge 3 commits intovllm-project:mainfrom
ROCm:rocm-deepep

Conversation

@lcskrishna
Copy link
Contributor

@lcskrishna lcskrishna commented Feb 17, 2026

This PR is to integrate changes required to run DeepEP as an all2allbackend on AMD GPUs.

co-authored by : @itej89

The following changes are performed:

  • The current codebase is modified to run DeepEP backend OOB on AMD GPUs without any issues.
  • FusedBatchedMoE kernels can run on AMD GPUs with float8_e4m3fnuz format added.

Next steps:

  • Docker update with ROCm/DeepEP installation steps.
  • Unit tests

Purpose

Test Plan

Test Result


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.
  • (Optional) Release notes update. If your change is user facing, please update the release notes draft in the Google Doc.

@github-actions
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 ask your reviewers to trigger select CI tests on top of fastcheck CI.

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.

If you have any questions, please reach out to us on Slack at https://slack.vllm.ai.

🚀

@mergify mergify bot added the rocm Related to AMD ROCm label Feb 17, 2026
@github-project-automation github-project-automation bot moved this to Todo in AMD Feb 17, 2026
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

This pull request enables DeepEP on ROCm for AMD GPUs by adding platform-specific logic, particularly for handling the float8_e4m3fnuz data type and adjusting API arguments. The changes are consistent across the modified files. My main feedback is to refactor a piece of duplicated code in all2all.py to improve maintainability.

@lcskrishna
Copy link
Contributor Author

lcskrishna commented Feb 17, 2026

cc: @itej89 @amathews-amd

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

rocm Related to AMD ROCm

Projects

Status: Todo

Development

Successfully merging this pull request may close these issues.

1 participant