Differences

This shows you the differences between two versions of the page.

--- blog:linux:routing_decisions_in_the_linux_kernel_2_caching [2025-01-18] – added IPv6 note to early demux Andrej Stender
+++ blog:linux:routing_decisions_in_the_linux_kernel_2_caching [2025-01-19] (current) – connected sockets in tx socket caching Andrej Stender
@@ Line 276: / Line 276: @@
 ===== Socked Caching (TX) =====
 This caching feature is being used on the local output path; thus, only for sending locally
-generated packets, not for received or forwarded packets. When a socket on the system
+generated packets, not for received or forwarded packets. When a connected/established
-(e.g. TCP or UDP socket, client or server)
+socket on the system (e.g. TCP or UDP socket, client or server)
 is sending data on the the network, then it is sufficient to only do a routing lookup
-for the very first packet it sends. After all, the destination IP address is the same
+for the very first packet it sends. After all, the destination IP address will be the same
 for all following packets it sends and so is the routing decision. Thus, the //routing
 decision// object, once obtained from the initial lookup, is being cached within the
@@ Line 557: / Line 557: @@
 to my attention and of course I'll then fix my content asap accordingly.
-//published 2022-07-31//, //last modified 2025-01-18//
+//published 2022-07-31//, //last modified 2025-01-19//