Skip to contentSkip to conversation

net/mlx5: document IP fragment matching limitations

PATCH In review Dariusz Sosnowski 4 participants 4 messages Jul 18, 2025 – Aug 18, 2025

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 net/mlx5: document IP fragment matching limitations

NVIDIA NICs do not support matching on packet headers appearing after IP header if the received packet is an IP fragment. This patch updates the relevant documentation.

Bugzilla ID: 1417

---
Depends-on: series-35735 ("rework mlx5 guide")

FYI - I added Bugzilla ticket ID just for reference. Patch does not resolve the issue, just adds missing documentation for existing limitation.

 doc/guides/nics/mlx5.rst | 7 +++++++
 1 file changed, 7 insertions(+)
doc/guides/nics/mlx5.rst +7 -0
index f29408eace..f58fea106a 100644
@@ -3305,6 +3305,13 @@ Limitations
 
 #. IP-in-IP is not supported with :ref:`HW steering <mlx5_hws>`.
 
+#. Matching on packet headers appearing after an IP header is not supported
+   if that packet is an IP fragment:
+
+   - For example: If a flow rule with pattern matching on L4 header contents is created,
+     and the first IP fragment is received,
+     then this IP fragment will miss on that flow rule.
+
 
 .. _mlx5_nat64:
 

--
2.39.5

#1 lore raw
Quoted 7 lines · On Fri, 18 Jul 2025 13:51:56 +0200 Dariusz Sosnowski <[email protected]>…

NVIDIA NICs do not support matching on packet headers appearing after IP header if the received packet is an IP fragment. This patch updates the relevant documentation.

Bugzilla ID: 1417

I suspect that is true of all NIC's because matching later fragments would require state that would not scale in HW.

Acked-by on v1 1/1
#2 lore raw
In reply to Dariusz Sosnowski

Hi,
@Stephen Hemminger, we don't know other NICs behavior. If all NICs behave the same, maybe the limitation can be considered to move to the common part.

Quoted 48 lines

-----Original Message-----
From: Dariusz Sosnowski <[email protected]>
Sent: Friday, July 18, 2025 7:52 PM
To: Slava Ovsiienko <[email protected]>; Bing Zhao <[email protected]>; Ori Kam <[email protected]>; Suanming Mou <[email protected]>; Matan Azrad <[email protected]>
Cc: [email protected]; NBU-Contact-Thomas Monjalon (EXTERNAL) <[email protected]>; Raslan Darawsheh <[email protected]>
Subject: [PATCH] net/mlx5: document IP fragment matching limitations

NVIDIA NICs do not support matching on packet headers appearing after IP header if the received packet is an IP fragment.
This patch updates the relevant documentation.

Bugzilla ID: 1417

---
Depends-on: series-35735 ("rework mlx5 guide")

FYI - I added Bugzilla ticket ID just for reference.
Patch does not resolve the issue, just adds missing documentation for existing limitation.

 doc/guides/nics/mlx5.rst | 7 +++++++
 1 file changed, 7 insertions(+)
doc/guides/nics/mlx5.rst index renamed from doc/guides/nics/mlx5.rst +0 -0

f29408eace..f58fea106a 100644

doc/guides/nics/mlx5.rst +1 -0
@@ -3305,6 +3305,13 @@ Limitations
 
 #. IP-in-IP is not supported with :ref:`HW steering <mlx5_hws>`.
 
+#. Matching on packet headers appearing after an IP header is not

supported

doc/guides/nics/mlx5.rst +3 -0
+   if that packet is an IP fragment:
+
+   - For example: If a flow rule with pattern matching on L4 header

contents is created,

doc/guides/nics/mlx5.rst +3 -1
+     and the first IP fragment is received,
+     then this IP fragment will miss on that flow rule.
+
 
 .. _mlx5_nat64:
 
--
Quoted 1 line

2.39.5

Thanks

#3 lore raw
In reply to Dariusz Sosnowski

Hi,

Quoted 6 lines · Dariusz Sosnowski

NVIDIA NICs do not support matching on packet headers appearing after IP header if the received packet is an IP fragment. This patch updates the relevant documentation.

Bugzilla ID: 1417

Quoted 8 lines

---
Depends-on: series-35735 ("rework mlx5 guide")

FYI - I added Bugzilla ticket ID just for reference. Patch does not resolve the issue, just adds missing documentation for existing limitation.

Patch applied to next-net-mlx,

Kindest regards
Raslan Darawsheh