[PATCH 2/2] doc: update MLX5 LRO limitation
Gregory Etelson
getelson at nvidia.com
Thu Nov 17 15:39:01 CET 2022
Maximal LRO message size must be multiply of 256.
Otherwise, TCP payload may not fit into a single WQE.
Cc: stable at dpdk.org
Signed-off-by: Gregory Etelson <getelson at nvidia.com>
Acked-by: Matan Azrad <matan at nvidia.com>
---
doc/guides/nics/mlx5.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index 4f0db21dde..98e0b24be4 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -278,6 +278,9 @@ Limitations
- No Tx metadata go to the E-Switch steering domain for the Flow group 0.
The flows within group 0 and set metadata action are rejected by hardware.
+- The driver rounds down the ``max_lro_pkt_size`` value in the port
+ configuration to a multiple of 256 due to HW limitation.
+
.. note::
MAC addresses not already present in the bridge table of the associated
--
2.34.1
More information about the stable
mailing list