A nice overview; thanks for sharing it!<p>I don't think that your claim that GRO is "a software implementation of a hardware optimization that is known as Large Receive Offloading (LRO)" is correct, though. GRO effectively replaces LRO [1]; it has fewer limitations (it works with non-TCP traffic and with bridging [2], for example). Drivers need to support it, but they are free to take advantage of hardware offloading/acceleration, and many do (including e.g. the ixgbe driver [3]).<p>----<p>[1] In terms of function, and in the sense that LRO could be removed if the drivers that were using LRO were updated to use GRO instead.<p>[2] Relevant bug: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=772317" rel="nofollow">https://bugzilla.redhat.com/show_bug.cgi?id=772317</a><p>[3] Which actually supports both LRO and GRO; if I recall, in older versions, bad things(tm) would sometimes happen if you had both enabled at the same time (whereas now the LRO setting is ignored if GRO is enabled).