Upgrade DeepGEMM to unify hopper with blackwell#9167
Upgrade DeepGEMM to unify hopper with blackwell#9167fzyzcjy wants to merge 65 commits intosgl-project:mainfrom
Conversation
There was a problem hiding this comment.
Summary of Changes
Hello @fzyzcjy, 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 upgrades the DeepGEMM integration to unify its behavior across different NVIDIA GPU architectures, specifically Hopper and Blackwell. It achieves this by removing the explicit recipe parameter from DeepGEMM function calls, implying that the underlying DeepGEMM library now handles the necessary optimizations internally, simplifying the API and ensuring consistent performance across target hardware.
Highlights
- DeepGEMM API Simplification: The
recipeparameter, previously used to specify DeepGEMM configurations for Blackwell architectures, has been removed fromforward_deepgemmandforward_deepgemm_maskedfunctions. - Unified DeepGEMM Operation: The
recipeparameter has also been removed from thegrouped_gemm_nt_f8f8bf16_maskedfunction, indicating a unified approach to DeepGEMM operations that no longer requires explicit architecture-specific tuning via this parameter.
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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.
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
-
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. ↩
There was a problem hiding this comment.
Code Review
This pull request refactors the DeepGEMM integration to unify the code paths for Hopper and Blackwell architectures. The changes primarily involve removing the recipe parameter from calls to grouped_gemm_nt_f8f8bf16_masked, which was specific to the Blackwell implementation. This simplifies the code in ep_moe/layer.py and deep_gemm_wrapper/entrypoint.py by removing conditional logic and parameters, leading to a cleaner and more maintainable implementation. The changes are consistent and appear correct, reflecting an update in the underlying deep_gemm library API. Overall, this is a good simplification and unification of the codebase.
|
This is currently blocked by: deepseek-ai/DeepGEMM#160 (comment) |
|
co author in #9340 |
Motivation
Remarks
gsm8k: for normal it is 93.6 and 93.9 (same as baseline), for ll it is 90.0 and 89.4 (same as 89.4 and 89.8 baseline - iirc months ago I have seen something like this but this case is not used by real users)
Commands
Modifications
Accuracy Tests
Benchmarking and Profiling
Checklist