Field noteOct 23, 20262 min read1 source

Fix mega_mhc split barriers under CUDA graph replay

In one minute

DeepSeek’s DeepGEMM repository merged pull request #478 on October 20, 2026, fixing `mega_mhc` split barriers during CUDA Graph replay.

What changed: A new DeepGEMM pull request fixes mega_mhc split-barrier behavior during CUDA graph replay.

The pull request says a graph kernel node retains the same %gridid on each replay, allowing a barrier state from an earlier execution to satisfy a later wait.

Under that condition, a Mix or Norm waiter can proceed before its m-block initialization CTA has started and read split partials from the previous replay. The change tags executions with an epoch rather than %gridid. It stores the epoch and an exit count in unused space in the first barrier line, so the host-side barrier buffer and compiled extension do not change; the pull request describes the change as requiring JIT headers only.

The reported validation ran on an NVIDIA B200, replaying one graph node while alternating two inputs and comparing every replay bit-for-bit with eager results. For a 33-token case with SM contention, incorrect outputs fell from 185 of 200 runs to zero of 400; listed 512-token and 8,192-token contended cases also reached zero of 400 after the fix. The source does not establish performance impact, wider hardware coverage, or a packaged DeepGEMM release containing the change.

Evidence / sources

  1. 1github.com/deepseek-ai/DeepGEMM/pull/478
All Field Notes

Next reads

Read next

Open the graph
  1. 01topicInferenceExplore the inference topic hub.
  2. 02topicComputeExplore the compute topic hub.
  3. 03topicAi InfrastructureExplore the ai-infrastructure topic hub.
  4. 04archiveField NotesOpen the latest editorial analysis.
  5. 05source ledgerSource LedgerInspect the public source evidence graph.
Who read this page?Machine requests, hidden until opened

Loading the privacy-safe route aggregate...

Open the JSON contract