VR2R-0652

回到這篇 SA Coverage

① SA Source

Context Before

image

Source: SemiAnalysis AI Networking Model ↗

Evidence

As the per GPU bandwidth continues to scale to 3.2T, it is not hard to imagine a 4-plane network using SN6800 switches, where each 3.2T GPU is split four ways to connect to four different switch boxes at 800G per link.

Context After

In fact, if you have not already noticed – there are strong parallels between the X800-Q3400 switch (non-CPO) explained earlier in the article and a CPO switch in that both facilitate high-radix, multi-plane networking architectures while encasing within the box complex cabling that saves customers on the hassle of cable management.

Outside of the NVIDIA ecosystem, the main switch ASIC players are Broadcom, which will be manufacturing the Tomahawk 6 and Tomahawk 6 CPO ASICs, as well as Cisco, which recently announced the G300 102.4T ASIC. There are two flavors of hyperscaler backend network deployments:

② Atomic Claim

在原文所述假設情境中,隨著每顆 GPU bandwidth 提升到 3.2T,可以設想使用 SN6800 switches 的 4-plane network:每顆 3.2T GPU 分成 4 路,以每條 800G link 連到 4 個不同 switch boxes。

  • Epistemic Mode: HYPOTHETICAL
  • Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/GPU",
        "label": "GPU"
      },
      "role": "processor"
    },
    {
      "node": {
        "id": "04_knowledge_base/SN6800",
        "label": "SN6800"
      },
      "role": "switch_platform"
    }
  ],
  "qualifiers": {
    "condition_text": "forward-looking topology scenario; switch planes and boxes are plain text; Imagined future four-plane SN6800 network at 3.2T per GPU",
    "numeric_mentions": [
      "3.2T",
      "4",
      "800G"
    ],
    "temporal_mentions": []
  },
  "relation_type": "SN6800_FOUR_PLANE_GPU_FANOUT_SCENARIO"
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
processorGPUGPU
switch_platformSN6800SN6800

⑤ V2 Draft(需要修正時直接編輯)

Inline repair

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

V2 Atomic Claim Draft

在原文所述假設情境中,隨著每顆 GPU bandwidth 提升到 3.2T,可以設想使用 SN6800 switches 的 4-plane network:每顆 3.2T GPU 分成 4 路,以每條 800G link 連到 4 個不同 switch boxes。

V2 Semantic Frame Draft

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/GPU",
        "label": "GPU"
      },
      "role": "processor"
    },
    {
      "node": {
        "id": "04_knowledge_base/SN6800",
        "label": "SN6800"
      },
      "role": "switch_platform"
    }
  ],
  "qualifiers": {
    "condition_text": "forward-looking topology scenario; switch planes and boxes are plain text; Imagined future four-plane SN6800 network at 3.2T per GPU",
    "numeric_mentions": [
      "3.2T",
      "4",
      "800G"
    ],
    "temporal_mentions": []
  },
  "relation_type": "SN6800_FOUR_PLANE_GPU_FANOUT_SCENARIO"
}

V2 Revision Metadata Draft

{
  "epistemic_mode": "HYPOTHETICAL",
  "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 才是正式決策。