<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Packetization on Nalar</title>
    <link>https://nalar.dev/tags/packetization/</link>
    <description>Recent content in Packetization on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 16 Sep 2026 00:00:00 +0700</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/packetization/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Linux TCP Autocorking Coalesces Consecutive Small Writes</title>
      <link>https://nalar.dev/linux-tcp-autocorking-coalesces-consecutive-small-writes/</link>
      <pubDate>Wed, 16 Sep 2026 00:00:00 +0700</pubDate>
      <guid>https://nalar.dev/linux-tcp-autocorking-coalesces-consecutive-small-writes/</guid>
      <description>&lt;p&gt;A small TCP write does not always trigger an immediate packet transmission on Linux. With TCP autocorking enabled, the stack can defer a new small send when an earlier packet from the same flow is still waiting in a qdisc or device transmit queue, giving a following write a chance to join the pending data.&lt;/p&gt;&#xA;&lt;p&gt;The mechanism targets packet count rather than application-visible buffering semantics. A successful &lt;code&gt;write()&lt;/code&gt; or &lt;code&gt;sendmsg()&lt;/code&gt; still reports bytes accepted by the socket; autocorking influences when queued bytes advance into transmission.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
