From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: [PATCH RFC 0/2] veth, bridge, and GSO maximums Date: Sun, 26 Nov 2017 10:17:47 -0800 Message-ID: <20171126181749.19288-1-sthemmin@microsoft.com> Cc: netdev@vger.kernel.org, Stephen Hemminger To: davem@davemloft.net, stephen@networkplumber.org Return-path: Received: from mail-pl0-f68.google.com ([209.85.160.68]:36396 "EHLO mail-pl0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751318AbdKZSR6 (ORCPT ); Sun, 26 Nov 2017 13:17:58 -0500 Received: by mail-pl0-f68.google.com with SMTP id b12so7118425plm.3 for ; Sun, 26 Nov 2017 10:17:58 -0800 (PST) Sender: netdev-owner@vger.kernel.org List-ID: This pair of patchesimproves the performance when running containers in an environment where underlying device has lower GSO maximum (such as Azure). With containers a veth pair is created and one end is attached to the bridge device. The bridge device correctly reports computes GSO parameters that are the minimum of the lower devices. The problem is that the other end of the veth device (in container) reports the full GSO size. This patch propogates the upper (bridge device) parameters to the other end of the veth device. Please consider it as alternative to the sysfs GSO changes. Stephen Hemminger (2): br: add notifier for when bridge changes it GSO maximums veth: propagate bridge GSO to peer drivers/net/veth.c | 72 +++++++++++++++++++++++++++++++++++++++++++++++ include/linux/netdevice.h | 1 + net/bridge/br_if.c | 7 +++++ 3 files changed, 80 insertions(+) -- 2.11.0