Skip to content

Add the AMD low-latency kernels section, aligned with the NVIDIA section - #3

Merged
Oasis-Git merged 5 commits into
Oasis-Git:blog/sglang-vendor-kernel-runtimefrom
kevin-mii:blog/amd-low-latency-section
Oct 19, 2026
Merged

Oasis-Git merged 5 commits into
Oasis-Git:blog/sglang-vendor-kernel-runtimefrom
kevin-mii:blog/amd-low-latency-section

Conversation

@kevin-mii

@kevin-mii kevin-mii commented Oct 19, 2026 •

Copy link
Copy Markdown

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:

    • the plugin and its flag (--monokernel-backend amd);
    • the low-concurrency problem: six verify rows per request, and about 1,300 kernels per DSpark cycle;
    • bold-lead technique paragraphs: two persistent launches per layer, overlapping stages inside a launch, and the all-reduce inside the kernel;
    • the serving configuration;
    • the reported AgentX results and the observed accuracy.

    Source links are pinned to sgl-amd-mono e952b22.

  • AgentX chart (amd-agentx-interactivity.svg), styled after nvidia-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.

    • K1 loads its projection weights ahead of the norm and exchanges no data across GPUs.
    • K2 runs attention, the output projection, the second mHC update, the router and the experts. The mHC mix weights and the shared expert load early, routed-expert weights load after routing, and the attention and MoE partial sums are pushed to every GPU as they are produced.

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

To check before publishing

  • A rerun of AgentX at 1, 4 and 8 sessions with the current sgl-amd-mono would make the chart match the plugin exactly.
  • Fixed acceptance at 3.51 is inferred from #43984 comparing against the AgentX baseline "with the same recipe", which uses the golden acceptance length. Confirm with the author.
  • GSM8K is 0.901 with the plugin and 0.911 without it (1,319 questions). The text reports these as observed results, as the NVIDIA section does.

🤖 Generated with Claude Code

kevin-mii and others added 3 commits October 19, 2026 01:22
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>
@kevin-mii kevin-mii changed the title Add the AMD low-latency kernels section and figures Add the AMD low-latency kernels section, aligned with the NVIDIA section Oct 19, 2026
kevin-mii and others added 2 commits October 19, 2026 01:44
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>
@Oasis-Git
Oasis-Git merged commit d562caa into Oasis-Git:blog/sglang-vendor-kernel-runtime Oct 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants