SA260324R-0244
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Oberon and Kyber Updates, Larger World Sizes Introduced, More Networking Updates - Line hint:
308
Context Before
Each 28.8T NVLink Switch has 144 lanes of 200G (simultaneous bi-directional) which means each Switch has 24 lanes of 200G going to each connector. Copper flyover cables are used to connect each switch to the midplane, as the distances involved are too long for PCB traces. This is also why the switches are further away from the midplane, to provide space for the routing of the flyover cables.
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
Nvidia is looking into using co-packaged Copper to reduce loss further, in case NPC doesn’t work. As far as we know Nvidia is telling supply chain to go for fully co-packaged copper.
② Atomic Claim
每顆 NVLink Switch chip 透過 flyover cable 連到 switch blade 邊緣的 connector(使用 144 DPs × 200Gbit/s bi-di=28.8Tbit/s),再由 connector 插入 midplane board。
- Epistemic Mode:
ASSERTED - Mapping Status:
PARTIAL
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/NVSwitch",
"label": "NVLink Switch"
},
"role": "switch"
},
{
"node": {
"id": "04_knowledge_base/Flyover cable",
"label": "flyover cable"
},
"role": "cable"
},
{
"node": {
"id": "04_knowledge_base/Midplane",
"label": "midplane"
},
"role": "midplane"
}
],
"qualifiers": {
"condition_text": "connector 與 switch blade 沒有 canonical entity",
"numeric_mentions": [
"144",
"200Gbit/s",
"28.8Tbit/s"
],
"temporal_mentions": []
},
"relation_type": "NVSWITCH_TO_MIDPLANE_VIA_FLYOVER"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| switch | NVLink Switch | NVSwitch |
| cable | flyover cable | 04_knowledge_base/Flyover cable |
| midplane | 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 才是正式決策。