[https://nvbugs/6095421][fix] Update resolve_moe_backend#14282
Conversation
DeepSeek-V3-Lite-fp8 disagg test hangs on GB300 because resolve_moe_backend() returns CUTLASS for non-GptOss MoE models, and the CUTLASS FP8_BLOCK_SCALES path uses a DeepGEMM JIT kernel that only supports Hopper (SM90). On Blackwell (SM100/103) the worker throws 'fp8 blockscale gemm only support Hopper' during warmup; the disagg parent then deadlocks waiting for MPI_READY. Route AUTO moe_backend to DEEPGEMM on SM100/103, which natively supports these architectures with FP8_BLOCK_SCALES. Signed-off-by: tensorrt-cicd <90828364+tensorrt-cicd@users.noreply.github.com>
Signed-off-by: tensorrt-cicd <90828364+tensorrt-cicd@users.noreply.github.com>
Signed-off-by: yuhangh <58161490+heyuhhh@users.noreply.github.com>
|
/bot run --disable-fail-fast |
📝 WalkthroughWalkthroughThis PR introduces quantization-aware MOE backend resolution by extending the ChangesQuantization-aware MOE Backend Selection
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Suggested reviewers
🚥 Pre-merge checks | ✅ 3 | ❌ 2❌ Failed checks (2 warnings)
✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
PR_Github #49042 [ run ] triggered by Bot. Commit: |
|
PR_Github #49042 [ run ] completed with state |
Signed-off-by: yuhangh <58161490+heyuhhh@users.noreply.github.com>
|
/bot run --disable-fail-fast |
|
PR_Github #49224 [ run ] triggered by Bot. Commit: |
|
PR_Github #49224 [ run ] completed with state |
Summary by CodeRabbit
New Features
Tests
Description
Follows PR#14182 to complete the fix
Test Coverage
PR Checklist
Please review the following before submitting your PR:
PR description clearly explains what and why. If using CodeRabbit's summary, please make sure it makes sense.
PR Follows TRT-LLM CODING GUIDELINES to the best of your knowledge.
Test cases are provided for new code paths (see test instructions)
If PR introduces API changes, an appropriate PR label is added - either
api-compatibleorapi-breaking. Forapi-breaking, includeBREAKINGin the PR title.Any new dependencies have been scanned for license and vulnerabilities
CODEOWNERS updated if ownership changes
Documentation updated as needed
Update tava architecture diagram if there is a significant design change in PR.
The reviewers assigned automatically/manually are appropriate for the PR.
Please check this after reviewing the above items as appropriate for this PR.
GitHub Bot Help
To see a list of available CI bot commands, please comment
/bot help.