[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20171206015041.GA9672@ssarabia-MOBL7.amr.corp.intel.com>
Date: Tue, 5 Dec 2017 17:50:41 -0800
From: Solio Sarabia <solio.sarabia@...el.com>
To: Stephen Hemminger <stephen@...workplumber.org>
Cc: netdev@...r.kernel.org, davem@...emloft.net,
eric.dumazet@...il.com, dsahern@...il.com, kys@...rosoft.com,
shiny.sebastian@...el.com,
Stephen Hemminger <sthemmin@...rosoft.com>
Subject: Re: [PATCH 2/2] veth: allow configuring GSO maximums
On Tue, Dec 05, 2017 at 05:25:10PM -0800, Stephen Hemminger wrote:
> On Tue, 5 Dec 2017 17:14:26 -0800
> Solio Sarabia <solio.sarabia@...el.com> wrote:
>
> > From: Stephen Hemminger <stephen@...workplumber.org>
> >
> > Veth's can be used in environments (like Azure) where the underlying
> > network device is impacted by large GSO packets. This patch allows
> > gso maximum values to be passed in when creating the device via
> > netlink.
> >
> > In theory, other pseudo devices could also use netlink attributes
> > to set GSO maximums but for now veth is what has been observed
> > to be an issue.
> >
> > Signed-off-by: Stephen Hemminger <sthemmin@...rosoft.com>
> > Signed-off-by: Solio Sarabia <solio.sarabia@...el.com>
>
> I am testing new version with changelink support
Ack, I second whatever version works best.
Will help to try newer patches.
Powered by blists - more mailing lists