On 1/14/2021 7:07 AM, Shiri Kuzin wrote:
The Geneve tunneling protocol is designed to allow the user to specify
some data context on the packet.
The GENEVE TLV (Type-Length-Variable) Option is the mean intended to
present the user data.
In order to support GENEVE TLV Option the new rte_flow item
"rte_flow_item_geneve_opt" is introduced.
The new item contains the values and masks for the following fields:
-option class
-option type
-length
-data
The usage example:
"flow create 0 ingress pattern eth / ipv4 / udp / geneve vni is 100 /
geneve-opt class is 5 length is 1 type is 0 data is 0x66998800 /
end actions count / drop / end"
New item will be added to testpmd to support raw encap/decap action.
v6:
- added testpmd support for GENEVE option length.
- updated setting GENEVE option length value.
v5:
- added Devx function to def file.
v4:
- fixed setting option length.
- fixed testpmd calculation of GENEVE option size.
- updated documentation.
v3:
- updated documentation.
v2:
- removed pedantic.
Shiri Kuzin (7):
lib/librte_ethdev: introduce GENEVE header TLV option item
common/mlx5: check GENEVE TLV support in HCA attributes
common/mlx5: create GENEVE TLV option object with DevX
net/mlx5: create GENEVE TLV option management
net/mlx5: add GENEVE TLV option flow validation
net/mlx5: add GENEVE TLV option flow translation
doc: update GENEVE TLV option support
Viacheslav Ovsiienko (2):
app/testpmd: add GENEVE option item support
app/testpmd: add GENEVE header option length support
Hi Shiri,
Can you please rebase on top of latest next-net, this set conflicts with GTP
patchset.
Thanks,
ferruh
