[None][fix] Remove unused WarpPolicy in MOE OneSided A2A to reduce ma… - #14539
[None][fix] Remove unused WarpPolicy in MOE OneSided A2A to reduce ma…#14539djns99 wants to merge 1 commit into
Conversation
…intenance and prevent silent regressions Signed-off-by: djns99 <40156487+djns99@users.noreply.github.com>
📝 WalkthroughWalkthroughThis PR enforces one-block-per-token mode as the exclusive scheduling strategy for MOE A2A operations. The environment utility function is hardcoded to return true with deprecation guidance, and kernel code removes WarpPolicy specialization entirely, keeping only BlockPolicy and simplifying shared-memory layout and launch logic accordingly. ChangesMOE A2A One-Block-Per-Token Mode Enforcement
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes 🚥 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 |
There was a problem hiding this comment.
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
cpp/tensorrt_llm/kernels/communicationKernels/moeAlltoAllKernels.cu (1)
1-2:⚠️ Potential issue | 🟡 Minor | ⚡ Quick winUpdate copyright year for modified file.
The file is being modified but the copyright year on line 2 still shows only
2025. Per coding guidelines, the year should be updated on modified files.Suggested fix
/* - * Copyright (c) 2025, NVIDIA CORPORATION. All rights reserved. + * Copyright (c) 2025-2026, NVIDIA CORPORATION. All rights reserved. *As per coding guidelines:
**/*.{cpp,cc,h,hpp,py,cu,cuh}: Include NVIDIA copyright header on ALL new files; update year on modified files.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@cpp/tensorrt_llm/kernels/communicationKernels/moeAlltoAllKernels.cu` around lines 1 - 2, Update the copyright header at the top-of-file comment to include the current year range (e.g., change "2025" to "2025-2026") so the modified file's header is current; edit the top comment block in moeAlltoAllKernels.cu (the file-level /* ... */ header) to reflect the updated year range and ensure formatting matches existing NVIDIA copyright header style.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Outside diff comments:
In `@cpp/tensorrt_llm/kernels/communicationKernels/moeAlltoAllKernels.cu`:
- Around line 1-2: Update the copyright header at the top-of-file comment to
include the current year range (e.g., change "2025" to "2025-2026") so the
modified file's header is current; edit the top comment block in
moeAlltoAllKernels.cu (the file-level /* ... */ header) to reflect the updated
year range and ensure formatting matches existing NVIDIA copyright header style.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 5749f47e-8912-4ca7-b30f-152cb4410723
📒 Files selected for processing (3)
cpp/tensorrt_llm/common/envUtils.cppcpp/tensorrt_llm/common/envUtils.hcpp/tensorrt_llm/kernels/communicationKernels/moeAlltoAllKernels.cu
|
@bobboli will close this in a future PR |
|
Superseded by #14550 |
…intenance and prevent silent regressions
Summary by CodeRabbit
Release Notes
TLLM_MOE_A2A_ONE_BLOCK_PER_TOKENwill emit a warning that the feature is always enabled.getEnvMoeA2AOneBlockPerToken()function.Description
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.