VR2R-0293

回到這篇 SA Coverage

① SA Source

Context Before

image

Source: Nvidia VR NVL72 Component BoM and Power Budget Model ↗

Evidence

For the GB200/GB300, the PCIe signal distance between the GPU/CPU and the CX-7/8 is shorter than the Ethernet/InfiniBand signal distance between the CX-7/8 and the OSFP cages. Previously – having to transmit a 200G Ethernet/InfiniBand signal from the NIC in the back half of the compute tray to the OSFP cage in the front of the compute tray necessitated the use of flyover cables as the signal loss over PCB at 200Gbit/s (uni-directional) per lane is too high.

Context After

But now that the NIC is closer to the OSFP cage, the lower speed PCIe Gen6 signal (64Gbit/s per lane uni-directional) travels the longer distance. By making the PCIe Gen6 signal longer, the signal can travel over PCB given that PCIe Gen6 has better signal integrity than the higher speed 200G Ethernet/InfiniBand signal.

PCB vs Flyover Cables

② Atomic Claim

過去,從 compute tray 後半部的 NIC,把 200G Ethernet/InfiniBand signal 傳到前端 OSFP cage 時,必須使用 flyover cables,因為 PCB 上每 lane 200Gbit/s(uni-directional)的 signal loss 太高。

  • Epistemic Mode: ASSERTED
  • Mapping Status: PARTIAL

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Compute Tray",
        "label": "compute tray"
      },
      "role": "system_context"
    },
    {
      "node": {
        "id": "04_knowledge_base/NIC",
        "label": "NIC"
      },
      "role": "network_device"
    },
    {
      "node": {
        "id": "04_knowledge_base/Ethernet",
        "label": "Ethernet"
      },
      "role": "network_protocol"
    },
    {
      "node": {
        "id": "04_knowledge_base/InfiniBand",
        "label": "InfiniBand"
      },
      "role": "network_protocol"
    },
    {
      "node": {
        "id": "04_knowledge_base/PCB",
        "label": "PCB"
      },
      "role": "pcb_medium"
    }
  ],
  "qualifiers": {
    "condition_text": "OSFP cage and flyover cable are plain text in source claim; per-lane rate is uni-directional",
    "numeric_mentions": [
      "200G",
      "200Gbit/s"
    ],
    "temporal_mentions": [
      "previously"
    ]
  },
  "relation_type": "HIGH_SPEED_NETWORK_SIGNAL_REQUIRES_FLYOVER_CABLE"
}

④ Canonical Entity Mapping

RoleSurface LabelCanonical Target
system_contextcompute tray04_knowledge_base/Compute Tray
network_deviceNICNIC
network_protocolEthernetEthernet
network_protocolInfiniBandInfiniBand
pcb_mediumPCBPCB

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

Inline repair

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

V2 Atomic Claim Draft

過去,從 compute tray 後半部的 NIC,把 200G Ethernet/InfiniBand signal 傳到前端 OSFP cage 時,必須使用 flyover cables,因為 PCB 上每 lane 200Gbit/s(uni-directional)的 signal loss 太高。

V2 Semantic Frame Draft

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "04_knowledge_base/Compute Tray",
        "label": "compute tray"
      },
      "role": "system_context"
    },
    {
      "node": {
        "id": "04_knowledge_base/NIC",
        "label": "NIC"
      },
      "role": "network_device"
    },
    {
      "node": {
        "id": "04_knowledge_base/Ethernet",
        "label": "Ethernet"
      },
      "role": "network_protocol"
    },
    {
      "node": {
        "id": "04_knowledge_base/InfiniBand",
        "label": "InfiniBand"
      },
      "role": "network_protocol"
    },
    {
      "node": {
        "id": "04_knowledge_base/PCB",
        "label": "PCB"
      },
      "role": "pcb_medium"
    }
  ],
  "qualifiers": {
    "condition_text": "OSFP cage and flyover cable are plain text in source claim; per-lane rate is uni-directional",
    "numeric_mentions": [
      "200G",
      "200Gbit/s"
    ],
    "temporal_mentions": [
      "previously"
    ]
  },
  "relation_type": "HIGH_SPEED_NETWORK_SIGNAL_REQUIRES_FLYOVER_CABLE"
}

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 才是正式決策。