<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>PASID on Nalar</title>
    <link>https://nalar.dev/tags/pasid/</link>
    <description>Recent content in PASID 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/pasid/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PCIe PASID Lets One Device Carry Multiple Address-Space Contexts</title>
      <link>https://nalar.dev/pcie-pasid-lets-one-device-carry-multiple-address-space-contexts/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/pcie-pasid-lets-one-device-carry-multiple-address-space-contexts/</guid>
      <description>&lt;h1 id=&#34;pcie-pasid-lets-one-device-carry-multiple-address-space-contexts&#34;&gt;PCIe PASID Lets One Device Carry Multiple Address-Space Contexts&lt;/h1&gt;&#xA;&lt;p&gt;A PCIe function normally has a Requester ID derived from its bus, device, and function identity. That identifier tells platform components which function issued a transaction, but it is too coarse when one device serves work from several process address spaces at the same time.&lt;/p&gt;&#xA;&lt;p&gt;Process Address Space ID (PASID) adds another identity field to the transaction path. A PASID can select an address-space context beneath the same device function, allowing the IOMMU to distinguish memory traffic that belongs to different processes without requiring a separate PCIe function for each one.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
