<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Interrupts on Nalar</title>
    <link>https://nalar.dev/tags/interrupts/</link>
    <description>Recent content in Interrupts on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 17 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/interrupts/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>NIC Interrupt Coalescing Trades CPU Overhead for Packet Latency</title>
      <link>https://nalar.dev/nic-interrupt-coalescing-trades-cpu-overhead-for-packet-latency/</link>
      <pubDate>Thu, 17 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/nic-interrupt-coalescing-trades-cpu-overhead-for-packet-latency/</guid>
      <description>&lt;p&gt;A network interface can receive packets faster than a CPU should service one hardware interrupt per packet. Interrupt coalescing addresses that mismatch by allowing the adapter to group completion notifications and interrupt the CPU less often.&lt;/p&gt;&#xA;&lt;p&gt;The tradeoff is explicit. Fewer interrupts reduce interrupt handling and scheduling pressure, but a packet may wait longer before software is told that receive work is ready. The best setting depends on packet rate, latency targets, CPU capacity, and the adapter&amp;rsquo;s coalescing controls.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
