[TRTLLM-11587][feat] Enable chunked prefix for Nemotron models on sm120#12414
Conversation
Signed-off-by: Pamela <179191831+pamelap-nvidia@users.noreply.github.com>
|
/bot run |
|
PR_Github #39749 [ run ] triggered by Bot. Commit: |
📝 WalkthroughWalkthroughKernel enumeration for SM120 flash attention is expanded to generate additional configurations producing bf16 output when input dtype is e4m3_fp32. The supported head_sizes for these MLA kernels increases from [192, 576] to [128, 192, 576], with the comment updated accordingly. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes 🚥 Pre-merge checks | ❌ 3❌ Failed checks (2 warnings, 1 inconclusive)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment Tip You can customize the tone of the review comments and chat replies.Configure the |
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/kernels/fmha_v2/setup.py (1)
1-2:⚠️ Potential issue | 🟠 MajorUpdate the SPDX copyright year for this modified file.
Line 1 still ends at
2025, but this file is modified in this PR and should be updated to include2026.As per coding guidelines: "Add NVIDIA copyright header on ALL new files, and update year on modified files".
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@cpp/kernels/fmha_v2/setup.py` around lines 1 - 2, Update the SPDX copyright header in cpp/kernels/fmha_v2/setup.py by changing the year range on the first line from "2020-2025" to "2020-2026" so the modified file reflects the current year per the project's header policy; ensure the SPDX-License-Identifier line remains unchanged.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Outside diff comments:
In `@cpp/kernels/fmha_v2/setup.py`:
- Around line 1-2: Update the SPDX copyright header in
cpp/kernels/fmha_v2/setup.py by changing the year range on the first line from
"2020-2025" to "2020-2026" so the modified file reflects the current year per
the project's header policy; ensure the SPDX-License-Identifier line remains
unchanged.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro
Run ID: 6e990c07-d676-4684-a57a-bd1df66c796e
📒 Files selected for processing (1)
cpp/kernels/fmha_v2/setup.py
|
/bot help |
GitHub Bot Help
Provide a user friendly way for developers to interact with a Jenkins server. Run See details below for each supported subcommand. Details
Launch build/test pipelines. All previously running jobs will be killed.
kill
Kill all running builds associated with pull request. skip
Skip testing for latest commit on pull request. reuse-pipeline
Reuse a previous pipeline to validate current commit. This action will also kill all currently running builds associated with the pull request. IMPORTANT NOTE: This is dangerous since lack of user care and validation can cause top of tree to break. |
|
PR_Github #39749 [ run ] completed with state |
|
/bot run --stage-list "Build-Docker-Images" |
|
PR_Github #39767 [ run ] triggered by Bot. Commit: |
|
/bot reuse-pipeline |
|
PR_Github #39767 [ run ] completed with state |
|
/bot reuse-pipeline |
|
PR_Github #39787 [ reuse-pipeline ] triggered by Bot. Commit: |
|
PR_Github #39787 [ reuse-pipeline ] completed with state |
Summary by CodeRabbit
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)
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.