Re: [ovs-discuss] kernel panic receiving flooded VXLAN traffic with OVS

On Mon, Dec 8, 2014 at 7:33 AM, Jesse Gross [off-list ref] wrote:

If you look at the implementation of GRO/TSO, I think you will see
that it does in fact faithfully reconstruct the original message and
path MTU discovery is preserved. On Linux systems, GRO is enabled by
default for all workloads - including those that do not result in
local termination such as bridging.

I will go back and test this again (it's been a while - we just run with
all offloads turned off by default now).  When we were having problems with
this we would find segmented TCP flows getting reassembled along the path
and then output with the local egress MTU (which was considerably larger
than that at the end stations), resulting in performance-crushing IP
fragmentation later in the path.

--
Nick