VR2R-0232
① SA Source
- Source: 開啟完整 SA 文章
- Section:
BlueField-4 - Line hint:
327
Context Before
KV cache grows linearly with sequence length and multiplicatively with workload parallelism, quickly expanding beyond what any single tier of memory was designed to hold. GPU HBM, while unmatched in bandwidth and latency, is not enough on its own to store KV especially for longer sequence length queries that are becoming popular between turns or tool calls. Host DRAM extends capacity but remains node-bound and limited in aggregate footprint and ultimately has limited capacity. Meanwhile, traditional shared storage—architected for durability rather than latency —has more access time and power overhead, making it unsuitable for participation in the decode loop.
As we noted in mid-January in our Memory Model note ↗, Nvidia’s ICMS inserts a new G3.5 tier between local SSD (G3) and shared storage (G4), optimized specifically for ephemeral, recomputable KV cache. The ICMS requires a dedicated networking layer designed exclusively for KV traffic. Wherever networking is used in this architecture, it is provisioned as a context memory network — isolated from general data movement and optimized for predictable decode latency.
Evidence
The challenge with this is that the volumes of SSDs going to ICMS / CMX are quite overblown by the industry. We worked through the math in the Memory model ↗ and Tokenomics model ↗.
Context After
BlueField-4 will be the silicon anchor of this third network. Positioned on the storage array, it terminates NVMe-oF and RDMA traffic at line rate and manages KV movement independently of host CPUs and GPUs. With 2×400G SerDes links providing 800Gb/s of bandwidth, integrated Grace CPU, and LPDDR, BlueField-4 would act as the controller for a distributed context memory fabric. In a preferred DGX-style configuration, a single BlueField-4 per tray may serve four Rubin processors, with the DPU dedicated purely to KV cache traffic and not shared with generic storage I/O.
The new CMX/ICMS ecosystem will likely include leading storage providers such as Weka, DDN, Dell Technologies, NetApp, VAST Data, and others.
② Atomic Claim
SemiAnalysis 認為，業界對流向 ICMS／CMX 的 SSD volumes 有相當程度的高估。
- Epistemic Mode:
ASSERTED - Mapping Status:
COMPLETE
③ Semantic Frame
{
"attribute": "ANALYST_VIEW_OF_SSD_VOLUME_EXPECTATIONS",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/Inference Context Memory Storage",
"label": "ICMS / CMX"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "analyst judgment",
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "industry SSD volume expectations for ICMS/CMX are quite overblown."
}
}④ Canonical Entity Mapping
| Role | Surface Label | Canonical Target |
|---|---|---|
| entity | ICMS / CMX | 04_knowledge_base/Inference Context Memory Storage |
⑤ V2 Draft（需要修正時直接編輯）
Inline repair
只編輯以下三個 Draft 區塊。完成後將
review_action設為REQUEST_REPAIR，再手動執行 Repair Preview。
執行腳本前，Draft 不會寫入 Claim Store 或 Graph。
V2 Atomic Claim Draft
SemiAnalysis 認為，業界對流向 ICMS／CMX 的 SSD volumes 有相當程度的高估。
V2 Semantic Frame Draft
{
"attribute": "ANALYST_VIEW_OF_SSD_VOLUME_EXPECTATIONS",
"context_nodes": [],
"entity": {
"id": "04_knowledge_base/Inference Context Memory Storage",
"label": "ICMS / CMX"
},
"frame_type": "ATTRIBUTE",
"qualifiers": {
"condition_text": "analyst judgment",
"numeric_mentions": [],
"temporal_mentions": []
},
"value": {
"numeric_mentions": [],
"value_text": "industry SSD volume expectations for ICMS/CMX are quite overblown."
}
}V2 Revision Metadata Draft
{
"epistemic_mode": "ASSERTED",
"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 才是正式決策。