From: Dmitry Kozlyuk Date: Wed, 30 Jun 2021 07:01:06 +0000 (+0300) Subject: doc: add limitation for ConnectX-4 with L2 in mlx5 guide X-Git-Url: http://git.droids-corp.org/?a=commitdiff_plain;h=e60561cc955ac01512a35ca309793e351cef3c9b;p=dpdk.git doc: add limitation for ConnectX-4 with L2 in mlx5 guide ConnectX-4 and ConnectX-4 Lx NICs require all L2 headers of transmitted packets to be inlined. By default only first 18 bytes are inlined, which is insufficient if additional encapsulation is used, like Q-in-Q. Thus, default settings caused such traffic to be dropepd on Tx. Document a recommendation to increase inlined data size in such cases. Fixes: 505f1fe426d3 ("net/mlx5: add Tx devargs") Cc: stable@dpdk.org Signed-off-by: Dmitry Kozlyuk Reviewed-by: Viacheslav Ovsiienko --- diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst index 0d96eec2bb..5b4bb13914 100644 --- a/doc/guides/nics/mlx5.rst +++ b/doc/guides/nics/mlx5.rst @@ -700,6 +700,13 @@ Driver options it is not recommended and may prevent NIC from sending packets over some configurations. + For ConnectX-4 and ConnectX-4 Lx NICs, automatically configured value + is insufficient for some traffic, because they require at least all L2 headers + to be inlined. For example, Q-in-Q adds 4 bytes to default 18 bytes + of Ethernet and VLAN, thus ``txq_inline_min`` must be set to 22. + MPLS would add 4 bytes per label. Final value must account for all possible + L2 encapsulation headers used in particular environment. + Please, note, this minimal data inlining disengages eMPW feature (Enhanced Multi-Packet Write), because last one does not support partial packet inlining. This is not very critical due to minimal data inlining is mostly required