Fp8 prefill attn kernel integration#18528
Conversation
Summary of ChangesHello @1am9trash, 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 integrates an FP8 prefill attention kernel to enhance performance by replacing the existing BF16 kernel. It introduces an environment variable for controlling this feature, adds new metadata generation logic, and modifies the attention forward pass to utilize FP8 inputs and specialized Highlights
🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console. Changelog
Activity
Using Gemini Code AssistThe 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 by creating a comment using either
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 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
|
There was a problem hiding this comment.
Code Review
This pull request integrates an FP8 prefill attention kernel to improve performance, controlled by the SGLANG_AITER_FP8_PREFILL_ATTN environment variable. The changes include adding new helper functions to generate metadata for the FP8 kernel and updating the forward_extend method to use this new path.
My review identifies a critical bug in the FP8 casting logic that could lead to a NameError, and another critical issue with hardcoded FP8 range values that could cause incorrect behavior on certain hardware. I've also pointed out some minor issues related to an unused variable and naming consistency to improve code quality.
|
Co-authored-by: @kkHuang-amd |
Co-authored-by: kkHuang-amd <wunhuang@amd.com>
Co-authored-by: kkHuang-amd <wunhuang@amd.com>
Co-authored-by: kkHuang-amd <wunhuang@amd.com>
Co-authored-by: kkHuang-amd <wunhuang@amd.com>
cc @HaiShaw, @kkHuang-amd
Motivation
Replace the current BF16 prefill kernel with an FP8 kernel to improve performance.
The FP8 path uses aiter kernels:
mla_prefill_ps_asm_fwdmla_reduce_v1 kernelModifications
SGLANG_AITER_FP8_PREFILL_ATTNenvironment variable to control whether FP8 prefill is enabled (enabled by default).init_forward_metadata().forward_extend(), cast BF16 inputs to FP8 (scale = 1) and call FP8 kernels.Accuracy Tests
gsm8k cmd:
python benchmark/gsm8k/bench_sglang.py --num-questions 2000 --parallel 2000 --port 9000GPQA cmd:
python -m sglang.test.run_eval --eval-name gpqa--port 9000 --num-examples 198 --max-tokens 65535 --repeat 8LiveBenchCode: not supported in sglang test.
Benchmarking and Profiling
server cmd:
Checklist
Review Process
/tag-run-ci-label,/rerun-failed-ci,/tag-and-rerun-ci