d/numam-dpdk
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

doc: add UDP/IPv4 GSO in guides

Browse Source 
This patch updates the programmer guide and testpmd user guide for
UDP/IPv4 GSO.

Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
Acked-by: Xiao Wang <xiao.w.wang@intel.com>
This commit is contained in:
Jiayu Hu 2018-07-06 09:02:24 +08:00 committed by Thomas Monjalon
parent aaacd052ce
commit 250c9eb3ca
2 changed files with 17 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/guides/prog_guide/generic_segmentation_offload_lib.rst
View File

@ -43,6 +43,7 @@ Limitations
#. Currently, the GSO library supports the following IPv4 packet types:
- TCP
- UDP
- VxLAN
- GRE
@ -146,6 +147,15 @@ TCP/IPv4 GSO
TCP/IPv4 GSO supports segmentation of suitably large TCP/IPv4 packets, which
may also contain an optional VLAN tag.
UDP/IPv4 GSO
~~~~~~~~~~~~
UDP/IPv4 GSO supports segmentation of suitably large UDP/IPv4 packets, which
may also contain an optional VLAN tag. UDP GSO is the same as IP fragmentation.
Specifically, UDP GSO treats the UDP header as a part of the payload and
does not modify it during segmentation. Therefore, after UDP GSO, only the
first output packet has the original UDP header, and others just have l2
and l3 headers.
VxLAN GSO
~~~~~~~~~
VxLAN packets GSO supports segmentation of suitably large VxLAN packets,

7
doc/guides/testpmd_app_ug/testpmd_funcs.rst
View File

@ -1059,6 +1059,13 @@ By default, GSO is disabled for all ports.
testpmd> csum set tcp hw <port_id>
UDP GSO is the same as IP fragmentation, which treats the UDP header
as the payload and does not modify it during segmentation. That is,
after UDP GSO, only the first output fragment has the original UDP
header. Therefore, users need to enable HW IP checksum calculation
and SW UDP checksum calculation for GSO-enabled ports, if they want
correct checksums for UDP/IPv4 packets.
set gso segsz
~~~~~~~~~~~~~