On Thu, Jun 30, 2016 at 1:06 AM, Pravin B Shelar <pshe...@ovn.org> wrote:
> Following patch backports updated iptunnel pull function.
> Also brings in following upstream fix:
>
> commit a09a4c8dd1ec7f830e1fb9e59eb72bddc965d168
> Author: Jesse Gross <je...@kernel.org>
>
> tunnels: Remove encapsulation offloads on decap.
>
> If a packet is either locally encapsulated or processed through GRO
> it is marked with the offloads that it requires. However, when it is
> decapsulated these tunnel offload indications are not removed. This
> means that if we receive an encapsulated TCP packet, aggregate it with
> GRO, decapsulate, and retransmit the resulting frame on a NIC that does
> not support encapsulation, we won't be able to take advantage of hardware
> offloads even though it is just a simple TCP packet at this point.
>
> This fixes the problem by stripping off encapsulation offload indications
> when packets are decapsulated.
>
> The performance impacts of this bug are significant. In a test where a
> Geneve encapsulated TCP stream is sent to a hypervisor, GRO'ed,
> decapsulated,
> and bridged to a VM performance is improved by 60% (5Gbps->8Gbps) as a
> result of avoiding unnecessary segmentation at the VM tap interface.
>
> Reported-by: Ramu Ramamurthy <srama...@linux.vnet.ibm.com>
> Fixes: 68c33163 ("v4 GRE: Add TCP segmentation offload for GRE")
> Signed-off-by: Jesse Gross <je...@kernel.org>
> Signed-off-by: David S. Miller <da...@davemloft.net>
>
> Signed-off-by: Pravin B Shelar <pshe...@ovn.org>
Acked-by: Jesse Gross <je...@kernel.org>
Since this patch bumps up the version that we'll use our backports
for, we'll need to remember that this effectively has a dependency on
later patches in the series. Otherwise, we'll have a situation like
with 2.4 where using the backport causes a regression in some cases.
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
