From: Andrew Melnychenko <hidden> Date: 2022-09-07 12:51:30
Added new offloads for TUN devices TUN_F_USO4 and TUN_F_USO6.
Technically they enable NETIF_F_GSO_UDP_L4
(and only if USO4 & USO6 are set simultaneously).
It allows the transmission of large UDP packets.
Different features USO4 and USO6 are required for qemu where Windows guests can
enable disable USO receives for IPv4 and IPv6 separately.
On the other side, Linux can't really differentiate USO4 and USO6, for now.
For now, to enable USO for TUN it requires enabling USO4 and USO6 together.
In the future, there would be a mechanism to control UDP_L4 GSO separately.
New types for virtio-net already in virtio-net specification:
https://github.com/oasis-tcs/virtio-spec/issues/120
Test it WIP Qemu https://github.com/daynix/qemu/tree/USOv3
Andrew (5):
uapi/linux/if_tun.h: Added new offload types for USO4/6.
driver/net/tun: Added features for USO.
uapi/linux/virtio_net.h: Added USO types.
linux/virtio_net.h: Support USO offload in vnet header.
drivers/net/virtio_net.c: Added USO support.
Andrew Melnychenko (1):
udp: allow header check for dodgy GSO_UDP_L4 packets.
drivers/net/tap.c | 10 ++++++++--
drivers/net/tun.c | 8 +++++++-
drivers/net/virtio_net.c | 19 +++++++++++++++----
include/linux/virtio_net.h | 9 +++++++++
include/uapi/linux/if_tun.h | 2 ++
include/uapi/linux/virtio_net.h | 5 +++++
net/ipv4/udp_offload.c | 2 +-
7 files changed, 47 insertions(+), 8 deletions(-)
--
2.37.2
From: Andrew Melnychenko <hidden> Date: 2022-09-07 12:51:53
Packets from TAP devices with USO offload converts
to GSO_UDP_L4 & GSO_DODGY sk buffers.
Added changes allow skipping segmentation for DODGY/ROBUST packets.
Signed-off-by: Jason Wang <redacted>
Signed-off-by: Andrew Melnychenko <redacted>
---
net/ipv4/udp_offload.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Andrew Melnychenko <hidden> Date: 2022-09-07 12:51:59
Added 2 additional offlloads for USO(IPv4 & IPv6).
Separate offloads are required for Windows VM guests,
g.e. Windows may set USO rx only for IPv4.
Signed-off-by: Andrew Melnychenko <redacted>
---
include/uapi/linux/if_tun.h | 2 ++
1 file changed, 2 insertions(+)
@@ -88,6 +88,8 @@#define TUN_F_TSO6 0x04 /* I can handle TSO for IPv6 packets */#define TUN_F_TSO_ECN 0x08 /* I can handle TSO with ECN bits. */#define TUN_F_UFO 0x10 /* I can handle UFO packets */+#define TUN_F_USO4 0x20 /* I can handle USO for IPv4 packets */+#define TUN_F_USO6 0x40 /* I can handle USO for IPv6 packets *//* Protocol info prepended to the packets (when IFF_NO_PI is not set) */#define TUN_PKT_STRIP 0x0001
From: Andrew Melnychenko <hidden> Date: 2022-09-07 12:52:01
Added support for USO4 and USO6.
For now, to "enable" USO, it's required to set both USO4 and USO6 simultaneously.
USO enables NETIF_F_GSO_UDP_L4.
Signed-off-by: Andrew Melnychenko <redacted>
---
drivers/net/tap.c | 10 ++++++++--
drivers/net/tun.c | 8 +++++++-
2 files changed, 15 insertions(+), 3 deletions(-)
@@ -957,6 +957,10 @@ static int set_offload(struct tap_queue *q, unsigned long arg)if(arg&TUN_F_TSO6)feature_mask|=NETIF_F_TSO6;}++/* TODO: for now USO4 and USO6 should work simultaneously */+if((arg&(TUN_F_USO4|TUN_F_USO6))==(TUN_F_USO4|TUN_F_USO6))+features|=NETIF_F_GSO_UDP_L4;}/* tun/tap driver inverts the usage for TSO offloads, where
@@ -967,7 +971,8 @@ static int set_offload(struct tap_queue *q, unsigned long arg)*WhenuserspaceturnsoffTSO,weturnoffGSO/LROsothat*user-spacewillnotreceiveTSOframes.*/-if(feature_mask&(NETIF_F_TSO|NETIF_F_TSO6))+if(feature_mask&(NETIF_F_TSO|NETIF_F_TSO6)||+(feature_mask&(TUN_F_USO4|TUN_F_USO6))==(TUN_F_USO4|TUN_F_USO6))features|=RX_OFFLOADS;elsefeatures&=~RX_OFFLOADS;
@@ -1091,7 +1096,8 @@ static long tap_ioctl(struct file *file, unsigned int cmd,caseTUNSETOFFLOAD:/* let the user check for future flags */if(arg&~(TUN_F_CSUM|TUN_F_TSO4|TUN_F_TSO6|-TUN_F_TSO_ECN|TUN_F_UFO))+TUN_F_TSO_ECN|TUN_F_UFO|+TUN_F_USO4|TUN_F_USO6))return-EINVAL;rtnl_lock();
@@ -2871,6 +2871,12 @@ static int set_offload(struct tun_struct *tun, unsigned long arg)}arg&=~TUN_F_UFO;++/* TODO: for now USO4 and USO6 should work simultaneously */+if(arg&TUN_F_USO4&&arg&TUN_F_USO6){+features|=NETIF_F_GSO_UDP_L4;+arg&=~(TUN_F_USO4|TUN_F_USO6);+}}/* This gives the user a way to test for new features in future by
From: Andrew Melnychenko <hidden> Date: 2022-09-07 12:52:25
Added new GSO type for USO: VIRTIO_NET_HDR_GSO_UDP_L4.
Feature VIRTIO_NET_F_HOST_USO allows to enable NETIF_F_GSO_UDP_L4.
Separated VIRTIO_NET_F_GUEST_USO4 & VIRTIO_NET_F_GUEST_USO6 features
required for Windows guests.
Signed-off-by: Andrew Melnychenko <redacted>
---
include/uapi/linux/virtio_net.h | 5 +++++
1 file changed, 5 insertions(+)
From: Andrew Melnychenko <hidden> Date: 2022-09-07 12:52:33
Now, it's possible to convert USO vnet packets from/to skb.
Added support for GSO_UDP_L4 offload.
Signed-off-by: Andrew Melnychenko <redacted>
---
include/linux/virtio_net.h | 9 +++++++++
1 file changed, 9 insertions(+)
From: Andrew Melnychenko <hidden> Date: 2022-09-07 12:52:57
Now, it possible to enable GSO_UDP_L4("tx-udp-segmentation") for VirtioNet.
Signed-off-by: Andrew Melnychenko <redacted>
---
drivers/net/virtio_net.c | 19 +++++++++++++++----
1 file changed, 15 insertions(+), 4 deletions(-)
From: David Ahern <dsahern@kernel.org> Date: 2022-09-08 00:44:24
On 9/7/22 6:50 AM, Andrew Melnychenko wrote:
Added new offloads for TUN devices TUN_F_USO4 and TUN_F_USO6.
Technically they enable NETIF_F_GSO_UDP_L4
(and only if USO4 & USO6 are set simultaneously).
It allows the transmission of large UDP packets.
Please spell out USO at least once in the cover letter to make sure the
acronym is clear.
Different features USO4 and USO6 are required for qemu where Windows guests can
enable disable USO receives for IPv4 and IPv6 separately.
On the other side, Linux can't really differentiate USO4 and USO6, for now.
Why is that and what is needed for Linux to differentiate between the 2
protocols?
For now, to enable USO for TUN it requires enabling USO4 and USO6 together.
In the future, there would be a mechanism to control UDP_L4 GSO separately.
New types for virtio-net already in virtio-net specification:
https://github.com/oasis-tcs/virtio-spec/issues/120
Test it WIP Qemu https://github.com/daynix/qemu/tree/USOv3
Andrew (5):
uapi/linux/if_tun.h: Added new offload types for USO4/6.
driver/net/tun: Added features for USO.
uapi/linux/virtio_net.h: Added USO types.
linux/virtio_net.h: Support USO offload in vnet header.
drivers/net/virtio_net.c: Added USO support.
Andrew Melnychenko (1):
udp: allow header check for dodgy GSO_UDP_L4 packets.
drivers/net/tap.c | 10 ++++++++--
drivers/net/tun.c | 8 +++++++-
drivers/net/virtio_net.c | 19 +++++++++++++++----
include/linux/virtio_net.h | 9 +++++++++
include/uapi/linux/if_tun.h | 2 ++
include/uapi/linux/virtio_net.h | 5 +++++
net/ipv4/udp_offload.c | 2 +-
7 files changed, 47 insertions(+), 8 deletions(-)
From: Andrew Melnichenko <hidden> Date: 2022-09-08 20:22:51
Hi all,
On Thu, Sep 8, 2022 at 3:44 AM David Ahern [off-list ref] wrote:
On 9/7/22 6:50 AM, Andrew Melnychenko wrote:
quoted
Added new offloads for TUN devices TUN_F_USO4 and TUN_F_USO6.
Technically they enable NETIF_F_GSO_UDP_L4
(and only if USO4 & USO6 are set simultaneously).
It allows the transmission of large UDP packets.
Please spell out USO at least once in the cover letter to make sure the
acronym is clear.
USO - UDP Segmentation Offload. Ability to split UDP packets into
several segments.
Allows sending/receiving big UDP packets. At some point, it looks like
UFO(fragmentation),
but each segment contains a UDP header.
quoted
Different features USO4 and USO6 are required for qemu where Windows guests can
enable disable USO receives for IPv4 and IPv6 separately.
On the other side, Linux can't really differentiate USO4 and USO6, for now.
Why is that and what is needed for Linux to differentiate between the 2
protocols?
Well, this feature requires for Windows VM guest interaction. Windows may have
a separate configuration for USO4/USO6. Currently, we support Windows guests
with enabled USO4 and USO6 simultaneously.
To implement this on Linux host, will require at least one additional
netdev feature
and changes in Linux network stack. Discussion about that will be in
the future after
some research.
quoted
For now, to enable USO for TUN it requires enabling USO4 and USO6 together.
In the future, there would be a mechanism to control UDP_L4 GSO separately.
New types for virtio-net already in virtio-net specification:
https://github.com/oasis-tcs/virtio-spec/issues/120
Test it WIP Qemu https://github.com/daynix/qemu/tree/USOv3
Andrew (5):
uapi/linux/if_tun.h: Added new offload types for USO4/6.
driver/net/tun: Added features for USO.
uapi/linux/virtio_net.h: Added USO types.
linux/virtio_net.h: Support USO offload in vnet header.
drivers/net/virtio_net.c: Added USO support.
Andrew Melnychenko (1):
udp: allow header check for dodgy GSO_UDP_L4 packets.
drivers/net/tap.c | 10 ++++++++--
drivers/net/tun.c | 8 +++++++-
drivers/net/virtio_net.c | 19 +++++++++++++++----
include/linux/virtio_net.h | 9 +++++++++
include/uapi/linux/if_tun.h | 2 ++
include/uapi/linux/virtio_net.h | 5 +++++
net/ipv4/udp_offload.c | 2 +-
7 files changed, 47 insertions(+), 8 deletions(-)