[v3,5/5] doc/mlx5: add IPv6 routing extension matching docs
Checks
Commit Message
Update mlx5 related document on IPv6 routing extension header
matching.
Signed-off-by: Rongwei Liu <rongweil@nvidia.com>
Acked-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
---
doc/guides/nics/features/default.ini | 1 +
doc/guides/nics/features/mlx5.ini | 1 +
doc/guides/nics/mlx5.rst | 10 ++++++++++
3 files changed, 12 insertions(+)
@@ -143,6 +143,7 @@ udp =
vlan =
vxlan =
vxlan_gpe =
+ipv6_routing_ext =
[rte_flow actions]
age =
@@ -89,6 +89,7 @@ vlan = Y
vxlan = Y
vxlan_gpe = Y
represented_port = Y
+ipv6_routing_ext = Y
[rte_flow actions]
age = I
@@ -106,6 +106,7 @@ Features
- Sub-Function representors.
- Sub-Function.
- Matching on represented port.
+- Matching on IPv6 routing extension header.
Limitations
@@ -174,6 +175,7 @@ Limitations
- ``-EAGAIN`` for ``rte_eth_dev_start()``.
- ``-EBUSY`` for ``rte_eth_dev_stop()``.
+ - Matching on ICMP6 following IPv6 routing extension header, should match ipv6_routing_ext_next_hdr instead of ICMP6.
- When using Verbs flow engine (``dv_flow_en`` = 0), flow pattern without any
specific VLAN will match for VLAN packets as well:
@@ -274,6 +276,14 @@ Limitations
extension header type = 0x85).
- Match on GTP extension header is not supported in group 0.
+- Match on IPv6 routing extension header supports the following fields only:
+
+ - type
+ - next_hdr
+ - segments_left
+
+ Only supports HW steering. (``dv_flow_en=2``)
+
- Flex item:
- Hardware support: BlueField-2.