diff options
| author | David S. Miller <davem@davemloft.net> | 2017-12-08 14:23:00 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2017-12-08 14:23:00 -0500 |
| commit | 62fd8b189e925156e63772d18d3add1797242dca (patch) | |
| tree | fd5c58a47be81e46ab6cedfef32e59b612df49b7 /drivers | |
| parent | 5a6a0445d1edb28fc89fd12b49cda2d5114e2665 (diff) | |
| parent | 72d24955b44a4039db54a1c252b5031969eeaac3 (diff) | |
| download | linux-62fd8b189e925156e63772d18d3add1797242dca.tar.bz2 | |
Merge branch 'veth-and-GSO-maximums'
Stephen Hemminger says:
====================
veth and GSO maximums
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.
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/net/veth.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/net/veth.c b/drivers/net/veth.c index f5438d0978ca..a69ad39ee57e 100644 --- a/drivers/net/veth.c +++ b/drivers/net/veth.c @@ -410,6 +410,9 @@ static int veth_newlink(struct net *src_net, struct net_device *dev, if (ifmp && (dev->ifindex != 0)) peer->ifindex = ifmp->ifi_index; + peer->gso_max_size = dev->gso_max_size; + peer->gso_max_segs = dev->gso_max_segs; + err = register_netdevice(peer); put_net(net); net = NULL; |