From mboxrd@z Thu Jan 1 00:00:00 1970 From: Solio Sarabia Subject: [PATCH 0/2] Allow changing device gso maximums Date: Tue, 5 Dec 2017 17:14:24 -0800 Message-ID: <1512522866-5544-1-git-send-email-solio.sarabia@intel.com> Cc: eric.dumazet@gmail.com, dsahern@gmail.com, kys@microsoft.com, shiny.sebastian@intel.com, solio.sarabia@intel.com To: netdev@vger.kernel.org, davem@davemloft.net, stephen@networkplumber.org Return-path: Received: from mga02.intel.com ([134.134.136.20]:54757 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753336AbdLFBSm (ORCPT ); Tue, 5 Dec 2017 20:18:42 -0500 Sender: netdev-owner@vger.kernel.org List-ID: Docker uses bridge/veth for its bridged network. veth sends tcp packets as big as 65536 (its default gso value), even when lower physical or synthetic devices expose a lower limit. This causes tcp fragmentation in the host, spinning more cpu cycles. The proposed solution is to allow user to tune gso settings, via iproute utils for example. Note: this enables changing gso for all interfaces, not limited to veth only. This series rebases Stephen's original patches [1]. It also fixes a minor issue when validating maximum gso_max_size, which can be in the range [0,65536]. Changes are validated with and without docker use cases. [1] https://marc.info/?l=linux-netdev&m=151217101428494&w=2 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 | 30 ++++++++++++++++++++++++++++++ 2 files changed, 50 insertions(+) -- 2.7.4