SA260324R-0065_r1

SA260324R-0065

① SA Source

• Source: 開啟完整 SA 文章
• Section: SRAM and Memory Hierarchy
• Line hint: 77

Context Before

This is why Nvidia has decided to combine these architectures to get the best of both worlds: accelerate parts of decode that are more latency sensitive and are not as memory heavy on a low-latency SRAM-heavy chip like the LPU, while memory hungry attention is performed on GPUs that come with a lot of fast (but not SRAM fast) memory capacity.

Evidence

This brings us to the Groq 3 LPU or LP30, with LPU gen 2 being skipped over.

Context After

This chip has no Nvidia design involvement. The SerDes issues affecting v2 appear to be fixed. Behind the paywall, we will reveal the SerDes IP vendor which may come as a surprise. Nvidia also announced an LP35 which is a minor refresh of the LP30 which will remain on SF4 and will require a new tapeout.

② Atomic Claim

接著是 Groq 第三代 LPU，也就是 LP30；第二代 LPU 被直接跳過。

• Epistemic Mode: ASSERTED
• Mapping Status: COMPLETE

③ Semantic Frame

{
  "frame_type": "NARY_RELATION",
  "participants": [
    {
      "node": {
        "id": "02_companies/Groq",
        "label": "Groq"
      },
      "role": "company"
    },
    {
      "node": {
        "id": "04_knowledge_base/Groq LPU",
        "label": "third-generation LPU"
      },
      "role": "architecture"
    },
    {
      "node": {
        "id": "04_knowledge_base/Groq LP30",
        "label": "LP30"
      },
      "role": "product"
    }
  ],
  "qualifiers": {
    "condition_text": "LPU gen 2 skipped over",
    "numeric_mentions": [
      "3",
      "2"
    ],
    "temporal_mentions": []
  },
  "relation_type": "PRODUCT_GENERATION_IDENTITY"
}

④ Canonical Entity Mapping

Role	Surface Label	Canonical Target
company	Groq	Groq
architecture	third-generation LPU	04_knowledge_base/Groq LPU
product	LP30	04_knowledge_base/Groq LP30

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