<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Event Notification on Nalar</title>
    <link>https://nalar.dev/tags/event-notification/</link>
    <description>Recent content in Event Notification on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 23 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/event-notification/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>EPOLLEXCLUSIVE Limits Wakeups Across epoll Instances</title>
      <link>https://nalar.dev/epollexclusive-limits-wakeups-across-epoll-instances/</link>
      <pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/epollexclusive-limits-wakeups-across-epoll-instances/</guid>
      <description>&lt;h1 id=&#34;epollexclusive-limits-wakeups-across-epoll-instances&#34;&gt;EPOLLEXCLUSIVE Limits Wakeups Across epoll Instances&lt;/h1&gt;&#xA;&lt;p&gt;&lt;code&gt;EPOLLEXCLUSIVE&lt;/code&gt; changes event distribution when several epoll instances register the same target file description. Without the flag, a readiness event can wake waiters associated with every interested epoll instance. With exclusive registrations, Linux can restrict that fan-out and reduce redundant wakeups.&lt;/p&gt;&#xA;&lt;p&gt;The flag does not make delivery single-consumer, does not assign ownership of the target, and does not replace application-level coordination. Its contract is narrower: among epoll instances that registered a target with &lt;code&gt;EPOLLEXCLUSIVE&lt;/code&gt;, one or more receive an event for a wakeup rather than requiring all of them to receive it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>signalfd Consumes Blocked Signals Through File Descriptor Reads</title>
      <link>https://nalar.dev/signalfd-consumes-blocked-signals-through-file-descriptor-reads/</link>
      <pubDate>Wed, 23 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/signalfd-consumes-blocked-signals-through-file-descriptor-reads/</guid>
      <description>&lt;h1 id=&#34;signalfd-consumes-blocked-signals-through-file-descriptor-reads&#34;&gt;signalfd Consumes Blocked Signals Through File Descriptor Reads&lt;/h1&gt;&#xA;&lt;p&gt;&lt;code&gt;signalfd()&lt;/code&gt; turns selected signal notifications into records that can be consumed with &lt;code&gt;read()&lt;/code&gt;. A matching pending signal makes the descriptor readable, which allows signal handling to share the same &lt;code&gt;poll()&lt;/code&gt;, &lt;code&gt;select()&lt;/code&gt;, or &lt;code&gt;epoll&lt;/code&gt; path as sockets, timers, and other descriptors.&lt;/p&gt;&#xA;&lt;p&gt;The descriptor does not redirect signals merely because its mask names them. Normal signal-mask rules still apply. In the usual design, the selected signals are blocked before they can be delivered through their ordinary dispositions, then a &lt;code&gt;signalfd&lt;/code&gt; reads the pending instances.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
