Repository navigation
Add the AMD low-latency kernels section, aligned with the NVIDIA section - #3
Merged
Oasis-Git merged 5 commits intoOct 19, 2026
Conversation
Fill the AMD subsection with DeepSeek-V4.1 on MI350 Series GPUs: why a batch-1 decode step is launch-bound, what mono kernels change, the K1/K2 layer split, FlyDSL, and AgentX results. Add Figure 1 (AgentX P90 interactivity at one user on MI355X) and a schematic timeline of one layer on the standard path and in Low-Latency Mode. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Routed-expert weights cannot load before the router chooses the experts. The diagram now shows what the kernels load ahead of their waits: the projection weights in K1, and the mHC mix weights and the shared expert in K2. K2 also gains the second mHC update and norm between the attention all-reduce and the router, and K1 is marked as exchanging no data across GPUs. The section text says the same. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Follow the NVIDIA section's structure: the plugin and its flag, the low-concurrency problem with six verify rows per request, bold-lead technique paragraphs with source links pinned to sgl-amd-mono e952b22, the serving configuration, reported results and observed accuracy. Restyle the AgentX chart after nvidia-static-decode.svg (orange off, blue on, ratio labels, setup subtitle, flag and source footnotes), add the four- and eight-session points from sglang#43984, and move it into the AMD section. The Figure 1 placeholder is left for the shared cross-vendor figure. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Remove the links to sglang PRs and the PR number in the chart's source line. Keep a single pinned link, to the push and reduce stages, where it shows how the all-reduce runs inside the kernel. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Replace "tagged flags" with what the kernels do: each value is stored with a tag for the current decode step, so the next stage, on the same GPU or another, starts as soon as the tag matches, with no separate flag or reset between steps. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fills in the AMD subsection of the Low-Latency Mode post. Its structure and chart style match the NVIDIA section in #2, so the two vendor sections read in parallel.
Changes
AMD Low-Latency Kernels (about 650 words), in the same order as the NVIDIA section:
--monokernel-backend amd);Source links are pinned to sgl-amd-mono
e952b22.AgentX chart (
amd-agentx-interactivity.svg), styled afternvidia-static-decode.svg: orange plugin off, blue plugin on, ratio labels, setup subtitle, and flag and source footnotes. It shows P90 interactivity at 1, 4 and 8 concurrent sessions on MI355X: 1.50x, 1.56x and 1.45x.Layer diagram (
amd-mono-layer.svg): a schematic timeline of one DeepSeek-V4.1 layer on the standard path and with the plugin, checked against the kernel code.The Figure 1 placeholder is left in place for the shared cross-vendor figure, as in #2. This PR only inserts into the AMD subsection, and merging it with #2 produces no conflicts.
Sources
e952b22.To check before publishing
🤖 Generated with Claude Code