<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>NAPI on Nalar</title>
    <link>https://nalar.dev/tags/napi/</link>
    <description>Recent content in NAPI on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 03 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/napi/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SO_BUSY_POLL Trades CPU Time for Earlier Linux Socket Receive Processing</title>
      <link>https://nalar.dev/so-busy-poll-trades-cpu-time-for-earlier-socket-receive-processing/</link>
      <pubDate>Sat, 03 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/so-busy-poll-trades-cpu-time-for-earlier-socket-receive-processing/</guid>
      <description>&lt;p&gt;A blocking receive on Linux normally sleeps when no data is ready and resumes after the networking path makes data available. With &lt;code&gt;SO_BUSY_POLL&lt;/code&gt;, the receive path may instead spend a bounded interval actively polling the relevant NAPI context for incoming packets. That interval exchanges CPU time for a chance to process an arrival before the ordinary interrupt-driven path wakes the task.&lt;/p&gt;&#xA;&lt;p&gt;The option does not turn a socket into a permanently polling endpoint. It supplies a busy-poll budget in microseconds, and the mechanism depends on receive history and network-device support.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
