<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Block-Devices on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/block-devices/</link>
    <description>Recent content in Block-Devices on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 18 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/block-devices/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>ublk vs NBD vs tcmu in 2026: Which Userspace Block Driver Actually Wins?</title>
      <link>https://www.pistack.xyz/posts/2026-11-18-ublk-vs-nbd-vs-tcmu-userspace-block-drivers/</link>
      <pubDate>Wed, 18 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-11-18-ublk-vs-nbd-vs-tcmu-userspace-block-drivers/</guid>
      <description>&lt;p&gt;Your kernel&amp;rsquo;s block layer is no longer the only place to implement a disk. Since the &lt;code&gt;ublk&lt;/code&gt; driver landed in mainline Linux 6.0, &amp;ldquo;userspace block device&amp;rdquo; stopped being a synonym for &amp;ldquo;slow NBD hack&amp;rdquo; and became a legitimate architecture choice: io_uring-native, multi-queue, and fast enough that distribution kernels now ship it by default. Meanwhile the two older options — NBD and tcmu — did not disappear. They kept their niches, and picking the wrong one costs you a rewrite six months later.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
