<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Device I/O on Nalar</title>
    <link>https://nalar.dev/tags/device-i/o/</link>
    <description>Recent content in Device I/O on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 01 Jan 0001 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/device-i/o/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PCIe Posted MMIO Writes Can Outlive the CPU Store That Issued Them</title>
      <link>https://nalar.dev/pcie-posted-mmio-writes-readback-completion/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/pcie-posted-mmio-writes-readback-completion/</guid>
      <description>&lt;p&gt;A CPU can retire or complete an MMIO store before the corresponding PCIe Memory Write has reached the target device. The gap exists because PCIe Memory Write requests are posted: the requester sends them without waiting for a completion packet from the completer.&lt;/p&gt;&#xA;&lt;p&gt;That property is useful for throughput, but it creates an important boundary. A software-visible store instruction, an ordering barrier, and device observation of the write are not automatically the same event.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
