clm_f11a98577f784d7a8159ff7bcfc91da7_r1

VR2-0219

① SA Source

• Source: 開啟完整 SA 文章
• Section: BlueField-4
• Line hint: 319

Context Before

Source: Nvidia VR NVL72 BoM and Power Budget Model ↗

Evidence

For most hyperscalers’ deployments, the BlueField-4 module will be replaced with their in-house frontend networking module or simply with a CX-9 which is cheaper

Context After

Speaking of BlueField-4, it is important to discuss the new offering Jensen highlighted at CES earlier this year: ICMS, or Inference Context Memory Storage — a platform that we hear may be rebranded to “CMX” at GTC. ICMS, or CMX, introduces a third, entirely separate network dedicated solely to context memory. CMX is a purpose-built KV cache fabric. As long-context inference pushes context windows toward millions of tokens and agentic concurrency scales across users and services, the current memory hierarchy used to store KVcache begins to look insufficient.

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.

② Atomic Claim

多數 hyperscalers 部署時，BlueField-4 module 預期會被自研 frontend networking module 取代，或直接改用成本較低的 CX-9。

• Epistemic Mode: EXPECTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "comparison_expression": "多數 hyperscalers 部署時，BlueField-4 module 預期會被自研 frontend networking module 取代，或直接改用成本較低的 CX-9。",
  "entities": [
    {
      "id": "04_knowledge_base/Hyperscaler",
      "label": "hyperscalers"
    },
    {
      "id": "04_knowledge_base/BlueField-4",
      "label": "BlueField-4"
    }
  ],
  "frame_type": "COMPARISON",
  "metric": "COST",
  "operator": "LESS_THAN",
  "qualifiers": {
    "condition_text": null,
    "numeric_mentions": [
      "4 m",
      "9"
    ],
    "temporal_mentions": []
  }
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
comparison_entity_0	hyperscalers	Hyperscaler
comparison_entity_1	BlueField-4	BlueField-4

⑤ 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 才是正式決策。