<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>ACS on Nalar</title>
    <link>https://nalar.dev/tags/acs/</link>
    <description>Recent content in ACS on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/acs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PCIe ACS Controls Whether Peer Traffic Can Bypass the IOMMU</title>
      <link>https://nalar.dev/pcie-acs-controls-peer-traffic-bypass-iommu/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/pcie-acs-controls-peer-traffic-bypass-iommu/</guid>
      <description>&lt;h1 id=&#34;pcie-acs-controls-whether-peer-traffic-can-bypass-the-iommu&#34;&gt;PCIe ACS Controls Whether Peer Traffic Can Bypass the IOMMU&lt;/h1&gt;&#xA;&lt;p&gt;An IOMMU can restrict DMA only for transactions that reach its translation and permission checks. PCI Express complicates that boundary because two endpoints under the same hierarchy can exchange peer-to-peer traffic without sending every transaction through the root complex. A switch may be able to route a request directly from one downstream port to another.&lt;/p&gt;&#xA;&lt;p&gt;PCIe Access Control Services (ACS) adds controls for that routing boundary. Depending on the component and supported ACS features, the fabric can validate a request, block selected translated traffic, redirect peer requests or completions upstream, or constrain their egress. The result is not merely a routing preference. ACS can determine whether two devices are separable at the IOMMU boundary.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
