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

doc: add GRO limitations in programmers guide

Browse Source 
This patch adds GRO limitations in the programmer guide.

Fixes: 2c900d0905 ("doc: add GRO guide")
Cc: stable@dpdk.org

Signed-off-by: Jiayu Hu <jiayu.hu@intel.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
This commit is contained in:
Jiayu Hu 2019-01-16 10:13:42 +08:00 committed by Thomas Monjalon
parent 7ccc7a05d6
commit 5bd5f7b3ae
1 changed files with 19 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
doc/guides/prog_guide/generic_receive_offload_lib.rst
View File

@ -191,3 +191,22 @@ Header fields deciding if packets are neighbors include:
ignore IPv4 ID fields for the packets whose DF bit is 1.
Additionally, packets which have different value of DF bit can't
be merged.
GRO Library Limitations
-----------------------
- GRO library uses MBUF->l2_len/l3_len/l4_len/outer_l2_len/
outer_l3_len/packet_type to get protocol headers for the
input packet, rather than parsing the packet header. Therefore,
before call GRO APIs to merge packets, user applications
must set MBUF->l2_len/l3_len/l4_len/outer_l2_len/outer_l3_len/
packet_type to the same values as the protocol headers of the
packet.
- GRO library doesn't support to process the packets with IPv4
Options or VLAN tagged.
- GRO library just supports to process the packet organized
in a single MBUF. If the input packet consists of multiple
MBUFs (i.e. chained MBUFs), GRO reassembly behaviors are
unknown.