doc: update IPv6 5-tuple matching limitation
PATCH 1/1 doc: update IPv6 5-tuple matching limitation
Update IPv6 5-tuple matching limitation,
in newer HW, IPv6 5-tuple matching is
supported.
Signed-off-by Maayan Kashani <[email protected]>
Acked-by Bing Zhao <[email protected]>
--- doc/guides/nics/mlx5.rst | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-)
doc/guides/nics/mlx5.rst +7 -3
@@ -1381,8 +1381,6 @@ Limitations - ``-EAGAIN`` for ``rte_eth_dev_start()``. - ``-EBUSY`` for ``rte_eth_dev_stop()``. -#. Partial match with item template is not supported. - #. The supported actions order is as below:: MARK (a)
@@ -3324,7 +3322,13 @@ See :ref:`mlx5_firmware_config` for more details about the flex parser profile. Limitations ^^^^^^^^^^^ -#. IPv6 5-tuple matching is not supported with :ref:`HW steering <mlx5_hws>`. +#. IPv6 5-tuple matching is supported with :ref:`HW steering <mlx5_hws>` + from ConnectX-8/BlueField-3. + Previous NICs support matching on either IPv6 src or dst in a rule. + In general, the matching limitation is related to the number of DWORDS: + older hardware supports up to 5 DWORDS for matching, + while newer hardware (ConnectX-8/BlueField-3 and up) + supports up to 11 DWORDS for matching. #. IPv6 multicast messages are not supported on VM, while promiscuous mode and allmulticast mode are both set to off.
Signature · 1 line
2.21.0
Hi,
Quoted 6 lines · Maayan Kashani
Update IPv6 5-tuple matching limitation,
in newer HW, IPv6 5-tuple matching is
supported.Signed-off-by Maayan Kashani <[email protected]>Acked-by Bing Zhao <[email protected]>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh