<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Posts on Packet Catcher</title>
    <link>https://mktry.com/posts/</link>
    <description>Recent content in Posts on Packet Catcher</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Fri, 10 Apr 2026 08:00:00 +0800</lastBuildDate>
    <atom:link href="https://mktry.com/posts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>PFC Headroom Testing in SONiC with Snappi</title>
      <link>https://mktry.com/posts/pfc-headroom-test-with-snappi/</link>
      <pubDate>Fri, 10 Apr 2026 08:00:00 +0800</pubDate>
      <guid>https://mktry.com/posts/pfc-headroom-test-with-snappi/</guid>
      <description>&lt;h2 id=&#34;background&#34;&gt;Background&lt;/h2&gt;
&lt;p&gt;In data center networks, &lt;strong&gt;Priority Flow Control (PFC)&lt;/strong&gt; is a mechanism defined in IEEE 802.1Qbb that allows a receiver to pause traffic on a per-priority basis, enabling lossless transport for high-priority traffic such as RDMA over Converged Ethernet (RoCE).&lt;/p&gt;
&lt;p&gt;When a switch&amp;rsquo;s ingress buffer starts filling up, it sends a &lt;strong&gt;PFC PAUSE frame&lt;/strong&gt; to the upstream sender. However, there is always some in-flight traffic between the time the PAUSE is sent and when the sender actually stops — this in-flight data must be absorbed by the &lt;strong&gt;headroom buffer&lt;/strong&gt;.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
