netdev - Re: USO / UFO status ?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+FuTSdVsTgcpB9=CEb=O369qUR58d-zEz5vmv+9nR+-DJFM6Q@mail.gmail.com>
Date:   Wed, 30 Oct 2019 20:48:47 +0100
From:   Willem de Bruijn <willemdebruijn.kernel@...il.com>
To:     Jose Abreu <Jose.Abreu@...opsys.com>
Cc:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        Joao Pinto <Joao.Pinto@...opsys.com>
Subject: Re: USO / UFO status ?

On Wed, Oct 30, 2019 at 3:16 PM Jose Abreu <Jose.Abreu@...opsys.com> wrote:
>
> Hi netdev,
>
> What's the status of UDP Segmentation Offload (USO) and UDP
> Fragmentation Offloading (UFO) on current mainline ?
>
> I see that NETIF_F_GSO_UDP_L4 is only supported by Mellanox NIC's but I
> also saw some patches from Intel submitting the support. Is there any
> tool to test this (besides the -net selftests) ?

UDP segmentation offload with UDP_SEGMENT is always available with
software segmentation. The only driver with hardware offload (USO)
merged so far is indeed mlx5. Patches for various Intel NICs are in
review.

UFO is no longer generated by the protocol stack. It is still accepted
as input from legacy userspace with VIRTIO_NET_HDR_GSO_UDP.