patch 'net/mlx5: fix flow mark reading after reconfigure' has been queued to stable release 23.11.7
Shani Peretz
shperetz at nvidia.com
Wed Apr 15 11:59:16 CEST 2026
Hi,
FYI, your patch has been queued to stable release 23.11.7
Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet.
It will be pushed if I get no objections before 04/19/26. So please
shout if anyone has objections.
Also note that after the patch there's a diff of the upstream commit vs the
patch applied to the branch. This will indicate if there was any rebasing
needed to apply to the stable branch. If there were code changes for rebasing
(ie: not only metadata diffs), please double check that the rebase was
correctly done.
Queued patches are on a temporary branch at:
https://github.com/shanipr/dpdk-stable
This queued commit can be viewed at:
https://github.com/shanipr/dpdk-stable/commit/78984d268bbd2dd23c01589ace23d47e02e27652
Thanks.
Shani
---
>From 78984d268bbd2dd23c01589ace23d47e02e27652 Mon Sep 17 00:00:00 2001
From: Dariusz Sosnowski <dsosnowski at nvidia.com>
Date: Wed, 11 Feb 2026 09:12:38 +0100
Subject: [PATCH] net/mlx5: fix flow mark reading after reconfigure
[ upstream commit e6440647436ba5011de84db8dd1bbb46e96425fe ]
mlx5 PMD supports flow mark action which attaches additional
metadata to received packets. This metadata is stored
in the rte_mbuf in hash.fdir.hi field and applications
are notified about it with RTE_MBUF_F_RX_FDIR mbuf flag.
When working with HW Steering flow engine,
mlx5 PMD reads the HW completion entry field with flow mark value
if and only if at least one template table with flow mark action
was created.
Whenever table was created mlx5 PMD updated the private
data of each Rx queue to inform
Rx burst function to read HW field.
Whenever application reconfigures any of the Rx queues
through additional call to rte_eth_rx_queue_setup(),
this private Rx queue data is reset, but information
about existence of flow mark was not restored by PMD.
As a result, reconfiguration caused applications
to not receive flow mark metadata.
This patch fixes that behavior. Whenever port is started,
PMD will check if flow mark action is used and update
relevant private Rx queue data struct.
Fixes: 1deadfd709f5 ("net/mlx5: add HW mark action")
Signed-off-by: Dariusz Sosnowski <dsosnowski at nvidia.com>
Acked-by: Bing Zhao <bingz at nvidia.com>
---
drivers/net/mlx5/mlx5_flow.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/mlx5/mlx5_flow.c b/drivers/net/mlx5/mlx5_flow.c
index e955e41ee1..ec70c542bd 100644
--- a/drivers/net/mlx5/mlx5_flow.c
+++ b/drivers/net/mlx5/mlx5_flow.c
@@ -1987,6 +1987,7 @@ mlx5_flow_rxq_dynf_set(struct rte_eth_dev *dev)
data->flow_meta_port_mask = priv->sh->dv_meta_mask;
}
}
+ data->mark = !!priv->mark_enabled;
data->mark_flag = mark_flag;
}
}
--
2.43.0
---
Diff of the applied patch vs upstream commit (please double-check if non-empty:
---
--- - 2026-04-14 14:44:30.395195524 +0300
+++ 0015-net-mlx5-fix-flow-mark-reading-after-reconfigure.patch 2026-04-14 14:44:28.465453000 +0300
@@ -1 +1 @@
-From e6440647436ba5011de84db8dd1bbb46e96425fe Mon Sep 17 00:00:00 2001
+From 78984d268bbd2dd23c01589ace23d47e02e27652 Mon Sep 17 00:00:00 2001
@@ -5,0 +6,2 @@
+[ upstream commit e6440647436ba5011de84db8dd1bbb46e96425fe ]
+
@@ -31 +32,0 @@
-Cc: stable at dpdk.org
@@ -40 +41 @@
-index fddd309171..7df64d634d 100644
+index e955e41ee1..ec70c542bd 100644
@@ -43 +44 @@
-@@ -1898,6 +1898,7 @@ mlx5_flow_rxq_dynf_set(struct rte_eth_dev *dev)
+@@ -1987,6 +1987,7 @@ mlx5_flow_rxq_dynf_set(struct rte_eth_dev *dev)
More information about the stable
mailing list