<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Eventfd on Nalar</title>
    <link>https://nalar.dev/tags/eventfd/</link>
    <description>Recent content in Eventfd on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Fri, 18 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/eventfd/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>eventfd Aggregates Notifications in a Kernel Counter</title>
      <link>https://nalar.dev/eventfd-aggregates-notifications-in-a-kernel-counter/</link>
      <pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/eventfd-aggregates-notifications-in-a-kernel-counter/</guid>
      <description>&lt;p&gt;An &lt;code&gt;eventfd&lt;/code&gt; can absorb several notification writes before userspace services the descriptor. The kernel stores those writes in a 64-bit counter, so readiness represents pending counter state rather than a queue containing one record per notification.&lt;/p&gt;&#xA;&lt;p&gt;That distinction matters in event loops. A producer can add values while a consumer is occupied, and the next read can collapse accumulated state into one result. With &lt;code&gt;EFD_SEMAPHORE&lt;/code&gt;, the same object exposes a different consumption rule without changing its readiness model.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
