SA260324R-0195
① SA Source
- Source: 開啟完整 SA 文章
- Section:
Nvidia's CPO Roadmap - Line hint:
237
Context Before
CPO scale-up will be used to build the larger world size, connecting between the racks in a two-tier all to all network, though scale-up inside the racks will remain copper-based.
Evidence
When we reach the Feynman Generation, CPO usage will expand via another large world size rack, the NVL1152 which is formed by combining 8 Kyber racks.
Context After
While the Nvidia Technical Blog that outlines the rack configuration roadmap states that “NVIDIA Kyber will scale up into a massive all-to-all NVL1152 supercomputer using similar direct optical interconnects for rack-to-rack scale-up”, Jensen Huang in a Financial Analyst Q+A session did say that NVL1152 in Feynman would be “all CPO”. There is some disagreement on whether copper will still be used for scale-up within the rack or whether CPO will replace copper.
② Atomic Claim
進入 Feynman generation 後,CPO 的使用會擴展到另一個大型 world-size rack:NVL1152,由 8 個 Kyber rack 組成。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"frame_type": "NARY_RELATION",
"participants": [
{
"node": {
"id": "04_knowledge_base/NVIDIA Feynman Architecture",
"label": "Feynman"
},
"role": "generation"
},
{
"node": {
"id": "04_knowledge_base/CPO",
"label": "CPO"
},
"role": "technology"
},
{
"node": {
"id": "04_knowledge_base/NVL1152",
"label": "NVL1152"
},
"role": "system"
},
{
"node": {
"id": "04_knowledge_base/NVIDIA Kyber Rack",
"label": "Kyber rack"
},
"role": "rack"
}
],
"qualifiers": {
"condition_text": "NVL1152 由 8 個 Kyber racks 組成",
"numeric_mentions": [
"8",
"1152"
],
"temporal_mentions": [
"Feynman Generation"
]
},
"relation_type": "EXPANDS_CPO_TO_NVL1152"
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| generation | Feynman | 04_knowledge_base/NVIDIA Feynman Architecture |
| technology | CPO | CPO |
| system | NVL1152 | NVL1152 |
| rack | Kyber rack | 04_knowledge_base/NVIDIA Kyber Rack |
⑤ 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 才是正式決策。