From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH net-next 0/2] allow setting gso_maximum values Date: Fri, 1 Dec 2017 15:30:01 -0800 Message-ID: <20171201153001.4170f55d@xeon-e3> References: <20171201201158.25594-1-sthemmin@microsoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org, Stephen Hemminger To: davem@davemloft.net Return-path: Received: from mail-pf0-f195.google.com ([209.85.192.195]:36790 "EHLO mail-pf0-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751414AbdLAXaL (ORCPT ); Fri, 1 Dec 2017 18:30:11 -0500 Received: by mail-pf0-f195.google.com with SMTP id p84so5296981pfd.3 for ; Fri, 01 Dec 2017 15:30:10 -0800 (PST) In-Reply-To: <20171201201158.25594-1-sthemmin@microsoft.com> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, 1 Dec 2017 12:11:56 -0800 Stephen Hemminger wrote: > This is another way of addressing the GSO maximum performance issues for > containers on Azure. What happens is that the underlying infrastructure uses > a overlay network such that GSO packets over 64K - vlan header end up cause > either guest or host to have do expensive software copy and fragmentation. > > The netvsc driver reports GSO maximum settings correctly, the issue > is that containers on veth devices still have the larger settings. > One solution that was examined was propogating the values back > through the bridge device, but this does not work for cases where > virtual container network is done on L3. > > This patch set punts the problem to the orchestration layer that sets > up the container network. It also enables other virtual devices > to have configurable settings for GSO maximum. > > Stephen Hemminger (2): > rtnetlink: allow GSO maximums to be passed to device > veth: allow configuring GSO maximums > > drivers/net/veth.c | 20 ++++++++++++++++++++ > net/core/rtnetlink.c | 2 ++ > 2 files changed, 22 insertions(+) > I would like a confirmation from Intel that is doing Docker testing that this works for them before merging.