From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: [PATCH net-next v3 0/2] veth and GSO maximums Date: Thu, 7 Dec 2017 15:40:18 -0800 Message-ID: <20171207234020.18783-1-sthemmin@microsoft.com> Cc: netdev@vger.kernel.org, Stephen Hemminger To: davem@davemloft.net Return-path: Received: from mail-pf0-f193.google.com ([209.85.192.193]:36478 "EHLO mail-pf0-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751020AbdLGXkY (ORCPT ); Thu, 7 Dec 2017 18:40:24 -0500 Received: by mail-pf0-f193.google.com with SMTP id p84so5883153pfd.3 for ; Thu, 07 Dec 2017 15:40:24 -0800 (PST) Sender: netdev-owner@vger.kernel.org List-ID: 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. Stephen Hemminger (2): rtnetlink: allow GSO maximums to be set on device creation veth: set peer GSO values drivers/net/veth.c | 3 +++ net/core/rtnetlink.c | 34 ++++++++++++++++++++++++++++++++++ 2 files changed, 37 insertions(+) -- 2.11.0