<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Load Distribution on Nalar</title>
    <link>https://nalar.dev/tags/load-distribution/</link>
    <description>Recent content in Load Distribution on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 04 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/load-distribution/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SO_REUSEPORT Splits One Listen Address Across Multiple Linux Sockets</title>
      <link>https://nalar.dev/so-reuseport-splits-one-listen-address-across-multiple-linux-sockets/</link>
      <pubDate>Sun, 04 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/so-reuseport-splits-one-listen-address-across-multiple-linux-sockets/</guid>
      <description>&lt;p&gt;A conventional server owns one listening socket for a local address and port. SO_REUSEPORT changes that ownership boundary: multiple eligible sockets can bind the same address, and Linux selects a member of the reuseport group when traffic arrives.&lt;/p&gt;&#xA;&lt;p&gt;The option is useful when several worker threads or processes should receive traffic without sharing one accept or receive queue. It changes kernel-side socket selection, not the transport protocol carried on the network.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
