SA260324R-0321::SPLIT02
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Feynman NVL1152 Networking Topologies - Line hint:
397
Context Before
Now behind the paywall, we will share some more details on how all of this impacts the supply chain. Including beneficiaries of the LPX system, and the updated Kyber racks. We will also reveal a rack concept that Nvidia has yet to announce.
Feynman NVL1152 Networking Topologies
Evidence
Within each Feynman Kyber rack, we tentatively assume double the bandwidth per logical GPU and double the NVLink Switch bandwidth to 28.8T and 57.6T respectively. Though Jensen, in the Financial Q+A the day after the GTC Keynote, characterized NVL1152 as “all CPO”, the key technical blog outlining the new rack form factors ↗ only strictly referenced CPO for rack to rack interconnect. We will discuss the potential topography for both options.
Context After
To double the scale-up bandwidth using copper interconnect, NVIDIA would have to achieve a per lane bandwidth of 448Gbit/s uni-di (and implemented with simulatanous bi-directional SerDes so that each physical channel carries 448G of RX and 448G of TX) . However, this is a challenging feat as they would first have to prove the feasibility of 448Gb/s PAM4 SerDes at large volumes, then implement echo cancellation to achieve bidirectional bandwidth ↗, which is in itself extremely difficult. We believe Nvidia is going for 448G uni-di only.
② Atomic Claim
Nvidia 的 rack form-factor technical blog 僅明確提到 CPO 用於 NVL1152 的 rack-to-rack interconnect。
- Epistemic Mode:
ATTRIBUTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "TECHNICAL_BLOG_CPO_SCOPE",
"context_nodes": [
{
"id": "04_knowledge_base/CPO",
"label": "CPO"
}
],
"entity": {
"id": "04_knowledge_base/NVL1152",
"label": "NVL1152"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "Nvidia rack-form-factor technical blog",
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "CPO strictly referenced for rack-to-rack interconnect"
}
}④ Canonical Entity Mapping
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
Nvidia 的 rack form-factor technical blog 僅明確提到 CPO 用於 NVL1152 的 rack-to-rack interconnect。
V2 Semantic Frame Draft
{
"attribute": "TECHNICAL_BLOG_CPO_SCOPE",
"context_nodes": [
{
"id": "04_knowledge_base/CPO",
"label": "CPO"
}
],
"entity": {
"id": "04_knowledge_base/NVL1152",
"label": "NVL1152"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "Nvidia rack-form-factor technical blog",
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "CPO strictly referenced for rack-to-rack interconnect"
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "ATTRIBUTED",
"mapping_status": "COMPLETE"
}⑥ 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 才是正式決策。