NIEK2-0242
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Oberon and Kyber Updates, Larger World Sizes Introduced, More Networking Updates - Line hint:
303
Context Before
Source: SemiAnalysis Networking Model ↗
Evidence
Each NVLink Switch Chip connects via flyover cables to the connector (144 DPs used x 200 Gbit/s bi-di channel = 28.8Tbit/s) connectors at the edge of the switch blade, and these connectors plug into the midplane board
Context After
Rubin Ultra NVL288
Though not officially discussed by Nvidia at GTC 2026, an NVL288 concept has been explored within the supply chain. This would entail two NVL144 Kyber racks placed adjacent to each other, with a rack-to-rack copper backplane used to connect the two racks. One possibility is that all 288 GPUs are connected all to all, but this would require higher radix switches than the current NVLink 7 switches which only offer a maximum radix of 144 ports of 200G.
② Atomic Claim
每顆 NVLink Switch chip 透過 flyover cables 連到 switch blade 邊緣 connectors；使用 144 DPs × 200Gbit/s bi-di channel，可提供 28.8Tbit/s，這些 connectors 再插入 midplane board。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"comparison_expression": "每顆 NVLink Switch chip 透過 flyover cables 連到 switch blade 邊緣 connectors；使用 144 DPs × 200Gbit/s bi-di channel，可提供 28.8Tbit/s，這些 connectors 再插入 midplane board。",
"entities": [
{
"id": "04_knowledge_base/NVLink",
"label": "NVLink"
},
{
"id": "04_knowledge_base/Flyover cable",
"label": "flyover cables"
},
{
"id": "04_knowledge_base/Midplane",
"label": "midplane"
}
],
"frame_type": "COMPARISON",
"metric": "CONNECTOR_COUNT",
"operator": "MULTIPLE_OF",
"qualifiers": {
"condition_text": null,
"numeric_mentions": [
"144",
"200Gb",
"28.8Tb"
],
"temporal_mentions": []
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| comparison_entity_0 | NVLink | NVLink |
| comparison_entity_1 | flyover cables | 04_knowledge_base/Flyover cable |
| comparison_entity_2 | midplane | Midplane |
⑤ 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 才是正式決策。