<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Cxl on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/cxl/</link>
    <description>Recent content in Cxl on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 17 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/cxl/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CXL Memory Expansion in 2026: cxl-cli vs memtierd vs Kernel Auto-Tiering</title>
      <link>https://www.pistack.xyz/posts/2026-11-17-cxl-memory-expansion-cxl-cli-memtierd-tiering-guide/</link>
      <pubDate>Tue, 17 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-17-cxl-memory-expansion-cxl-cli-memtierd-tiering-guide/</guid>
      <description>&lt;p&gt;Your database fits in 512 GB of RAM. Your budget does not. That gap — not CPU, not storage — is what decides how many tenants you can pack onto a node in 2026, and it is why CXL memory expansion went from conference-talk curiosity to a line item in server refresh plans. A CXL Type-3 memory device lets you attach DRAM outside the CPU&amp;rsquo;s local memory channels: more capacity per socket, at a latency between local DRAM and NVMe, over a cache-coherent link.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
