Skip to content

Commit 6022b55

Browse files
mkp-rhigsilya
authored andcommitted
docs: Add tunnel support to TSO GRE documentation.
Previously support for tunnels was added to userspace TSO. However, the documentation was not updated appropriately. This patch adds VxLAN and Geneve as supported tunnels. Fixes: 084c808 ("userspace: Support VXLAN and GENEVE TSO.") Acked-by: David Marchand <david.marchand@redhat.com> Signed-off-by: Mike Pattrick <mkp@redhat.com> Signed-off-by: Ilya Maximets <i.maximets@ovn.org>
1 parent 6c77226 commit 6022b55

File tree

1 file changed

+9
-8
lines changed

1 file changed

+9
-8
lines changed

Documentation/topics/userspace-tso.rst

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -109,9 +109,9 @@ then started again. OvS will then report::
109109
Limitations
110110
~~~~~~~~~~~
111111

112-
The current OvS userspace `TSO` implementation supports flat and VLAN networks
113-
only (i.e. no support for `TSO` over tunneled connection [VxLAN, GRE, IPinIP,
114-
etc.]).
112+
The current OvS userspace `TSO` implementation supports flat, VLAN networks,
113+
and some tunneled connections. Currently only VxLAN and Geneve tunnels are
114+
supported.
115115

116116
The NIC driver must support and advertise checksum offload for TCP and UDP.
117117
However, SCTP is not mandatory because very few drivers advertised support
@@ -120,11 +120,12 @@ in Open vSwitch. Currently, if the NIC supports that, then the feature is
120120
enabled, otherwise TSO can still be enabled but SCTP packets sent to the NIC
121121
will be dropped.
122122

123-
There is no software implementation of TSO, so all ports attached to the
124-
datapath must support TSO or packets using that feature will be dropped
125-
on ports without TSO support. That also means guests using vhost-user
126-
in client mode will receive TSO packet regardless of TSO being enabled
127-
or disabled within the guest.
123+
There is no software implementation of TSO in conjunction with tunnels. So
124+
when VxLAN or Geneve tunnels are in use, all ports attached to the datapath
125+
must support TSO or packets using this combination of features will be dropped
126+
on ports without hardware TSO support. That also means guests using
127+
vhost-user in client mode will receive TSO packet regardless of TSO being
128+
enabled or disabled within the guest.
128129

129130
All kernel devices that use the raw socket interface (veth, for example)
130131
require the kernel commit 9d2f67e43b73 ("net/packet: fix packet drop as of

0 commit comments

Comments
 (0)