clm_3905b656b6a345e0a237d34a2ded72ce_r3

SA260324R-0120

回到這篇 SA Coverage

① SA Source

• Source: 開啟完整 SA 文章
• Section: GPU and LPU Integration: Attention FFN Disaggregation (AFD)
• Line hint: 119

Context Before

Source: SemiAnalysis

Evidence

To hide the communication latency of dispatch and combine, we employ ping pong pipeline parallelism. In addition to splitting batches into micro-batches and computation pipelining like standard pipeline parallelism, the tokens dispatched to the LPUs are combined back to the source GPUs, so they ping pong between the GPUs and the LPUs.

Context After

Source: MegaScale-Infer

② Atomic Claim

為了隱藏 dispatch 與 combine 的 communication latency，系統採用 ping-pong pipeline parallelism。

• Epistemic Mode: ASSERTED
• Mapping Status: PARTIAL

③ Semantic Frame

{
  "attribute": "USAGE",
  "context_nodes": [],
  "entity": {
    "id": "04_knowledge_base/Pipeline parallelism",
    "label": "pipeline parallelism"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": "dispatch 與 combine 在此 claim 沒有 canonical entity",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "以 ping-pong 方式使用，用來隱藏 dispatch 與 combine 的 communication latency。"
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
entity	pipeline parallelism	04_knowledge_base/Pipeline parallelism

⑤ V2 Draft（需要修正時直接編輯）

Inline repair

只編輯以下三個 Draft 區塊。完成後將 review_action 設為 REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。

V2 Atomic Claim Draft

為了隱藏 dispatch 與 combine 的 communication latency，系統採用 ping-pong pipeline parallelism。

V2 Semantic Frame Draft

{
  "attribute": "USAGE",
  "context_nodes": [],
  "entity": {
    "id": "04_knowledge_base/Pipeline parallelism",
    "label": "pipeline parallelism"
  },
  "frame_type": "ATTRIBUTE",
  "qualifiers": {
    "condition_text": "dispatch 與 combine 在此 claim 沒有 canonical entity",
    "numeric_mentions": [],
    "temporal_mentions": []
  },
  "value": {
    "numeric_mentions": [],
    "value_text": "以 ping-pong 方式使用，用來隱藏 dispatch 與 combine 的 communication latency。"
  }
}

V2 Revision Metadata Draft

{
  "epistemic_mode": "ASSERTED",
  "mapping_status": "PARTIAL"
}

⑥ Human Review

請在 Properties 逐項確認：

• 原文 → Atomic Claim 是否忠實
• Atomic Claim → Semantic Frame 是否忠實
• Canonical Entity mapping 是否正確
• Epistemic mode 是否保留原文語氣
• 最後選擇 review_action

Review state

Markdown 內文不是正式 approval。只有 Apply bridge 寫入的 Decision Ledger event 才是正式決策。