<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Kernel on Besterry — Linux &amp; DevOps Notes</title><link>https://besterry.com/tags/kernel/</link><description>Recent content in Kernel on Besterry — Linux &amp; DevOps Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 10 Feb 2024 00:00:00 +0000</lastBuildDate><atom:link href="https://besterry.com/tags/kernel/index.xml" rel="self" type="application/rss+xml"/><item><title>Linux Networking Deep Dive: From Socket to Wire</title><link>https://besterry.com/posts/linux-networking-deep-dive/</link><pubDate>Sat, 10 Feb 2024 00:00:00 +0000</pubDate><guid>https://besterry.com/posts/linux-networking-deep-dive/</guid><description>&lt;p&gt;Every time a packet leaves your Linux machine, it travels through a surprisingly long sequence of stages. Understanding this path helps enormously when debugging network issues.&lt;/p&gt;
&lt;h2 id="the-socket-layer"&gt;The socket layer&lt;/h2&gt;
&lt;p&gt;When your application calls &lt;code&gt;send()&lt;/code&gt; or &lt;code&gt;write()&lt;/code&gt; on a socket, the kernel&amp;rsquo;s socket layer takes over. For a TCP socket this means handing the data to &lt;code&gt;tcp_sendmsg()&lt;/code&gt;, which in turn enqueues it into the socket&amp;rsquo;s send buffer.&lt;/p&gt;
&lt;p&gt;You can observe the send queue depth with &lt;code&gt;ss -tipm&lt;/code&gt;:&lt;/p&gt;</description></item></channel></rss>