On Sat, Apr 30, 2016 at 1:43 AM, Alexander Duyck <adu...@mirantis.com> wrote: > This patch assumes that the mlx4 hardware will ignore existing IPv4/v6 > header fields for length and checksum as well as the length and checksum > fields for outer UDP headers.
Hi Alex, I see now the above text appearing in bunch of similar commit of yours, specifically to Intel drivers and mlx5... could you please elaborate a bit more what you mean here and what are the practical consequences of that characteristics? I got that right NETIF_F_GSO_UDP_TUNNEL_CSUM means that the HW can do segmentation for TCP packets encapsulated by UDP tunnel e.g VXLAN where the outer checksum is not zero. AFAIK, any other outer checksum value can't correctly be a constant... are you assuming here RCO or LCO? Or.
