# Re: \[PATCH net-next v3 0/2\] veth and GSO maximums

- From: David Miller \<davem@davemloft.net\>
- Date: 2017-12-08 19:23:25 
- List: netdev
- Page: https://ratatoskr.run/netdev/2017/12/11076061
- Thread: https://ratatoskr.run/netdev/2017/12/11075934/t.md

```text
From: Stephen Hemminger <stephen@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.
```