<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Sriov on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/sriov/</link>
    <description>Recent content in Sriov on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 12 May 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/sriov/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted SR-IOV Network Infrastructure: SR-IOV CNI vs SR-IOV Network Operator vs Multus CNI</title>
      <link>https://www.pistack.xyz/posts/2026-05-12-self-hosted-sr-iov-network-infrastructure-sriov-cni-operator-multus-guide/</link>
      <pubDate>Tue, 12 May 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-05-12-self-hosted-sr-iov-network-infrastructure-sriov-cni-operator-multus-guide/</guid>
      <description>&lt;p&gt;In Kubernetes environments, network performance is often the bottleneck for workloads that process high-throughput data &amp;ndash; packet capture, telecom core networks, NFV (Network Functions Virtualization), and real-time streaming. The default container networking model routes all traffic through a virtual bridge, adding latency and CPU overhead that can be unacceptable for these use cases.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
