From mboxrd@z Thu Jan  1 00:00:00 1970
From: Solio Sarabia <solio.sarabia@intel.com>
Subject: Re: [PATCH net-next v3 0/2] veth and GSO maximums
Date: Fri, 8 Dec 2017 15:50:25 -0800
Message-ID: <20171208235024.GA13336@ssarabia-MOBL7.amr.corp.intel.com>
References: <20171207234020.18783-1-sthemmin@microsoft.com>
 <20171208.142323.2060389926267620856.davem@davemloft.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Cc: netdev@vger.kernel.org, sthemmin@microsoft.com, davem@davemloft.net
To: stephen@networkplumber.org
Return-path: <netdev-owner@vger.kernel.org>
Received: from mga05.intel.com ([192.55.52.43]:45487 "EHLO mga05.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1753367AbdLHXu0 (ORCPT <rfc822;netdev@vger.kernel.org>);
        Fri, 8 Dec 2017 18:50:26 -0500
Content-Disposition: inline
In-Reply-To: <20171208.142323.2060389926267620856.davem@davemloft.net>
Sender: netdev-owner@vger.kernel.org
List-ID: <netdev.vger.kernel.org>

On Fri, Dec 08, 2017 at 02:23:23PM -0500, David Miller wrote:
> From: Stephen Hemminger <stephen@networkplumber.org>
> Date: Thu,  7 Dec 2017 15:40:18 -0800
> 
> > 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.
> 
> Ok, this is definitely a step forward.
> 
> Series applied, thanks Stephen.

Thanks.
Still not seeing the iproute2 patch though, either master or net-next.