http://bugs.dpdk.org/show_bug.cgi?id=1479
[email protected] ([email protected]) changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #1 from [email protected] ([email protected]) --- Hi, Siva, Sorry for the late response, You're correct that the mlx5 driver explicitly blocks the fragment matching patterns you're trying to use. For your use case (computing different RSS based on 5-tuple vs 3-tuple): Create two flow rules: One for ANY fragmented packets → RSS with 3-tuple (ipv4-frag) One for non-fragmented packets → RSS with 5-tuple (ipv4-tcp, ipv4-udp) The NIC will automatically: Use 3-tuple for fragments (only IP src/dst/protocol available) Use 5-tuple for non-fragments (full 5-tuple available) You cannot differentiate between first, middle, and last fragments in flow rules on ConnectX-6 DX. The hardware RSS engine already handles this correctly by design - fragmented packets can only use 3-tuple because port information is only in the first fragment, and may not be available to all fragments. -- You are receiving this mail because: You are the assignee for the bug.
