From: Stephen Hemminger <step...@networkplumber.org> Date: Thu, 7 Dec 2017 15:40:18 -0800
> This is the more general way to solving the issue of GSO limits > not being set correctly for containers on Azure. If a GSO packet > is sent to host that exceeds the limit (reported by NDIS), then > the host is forced to do segmentation in software which has noticeable > performance impact. > > The core rtnetlink infrastructure already has the messages and > infrastructure to allow changing gso limits. With an updated iproute2 > the following already works: > # ip li set dev dummy0 gso_max_size 30000 > > These patches are about making it easier with veth. Ok, this is definitely a step forward. Series applied, thanks Stephen.
