Re: [PATCH net-next v3 0/2] veth and GSO maximums

2017-12-08 Thread Stephen Hemminger
On Fri, 8 Dec 2017 15:50:25 -0800 Solio Sarabia wrote: > On Fri, Dec 08, 2017 at 02:23:23PM -0500, David Miller wrote: > > From: Stephen Hemminger > > 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

Re: [PATCH net-next v3 0/2] veth and GSO maximums

2017-12-08 Thread Solio Sarabia
On Fri, Dec 08, 2017 at 02:23:23PM -0500, David Miller wrote: > From: Stephen Hemminger > 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 excee

Re: [PATCH net-next v3 0/2] veth and GSO maximums

2017-12-08 Thread David Miller
From: Stephen Hemminger 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 segmentat

[PATCH net-next v3 0/2] veth and GSO maximums

2017-12-07 Thread Stephen Hemminger
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 rtnet