From: Maayan Kashani <mkashani@nvidia.com>
To: <dev@dpdk.org>
Cc: <dsosnowski@nvidia.com>, <viacheslavo@nvidia.com>,
<bingz@nvidia.com>, <orika@nvidia.com>, <suanmingm@nvidia.com>,
<matan@nvidia.com>, "Maayan Kashani" <mkashani@nvidia.com>,
<stable@dpdk.org>
Subject: [PATCH] net/mlx5: fix external egress group translation
Date: Mon, 9 Nov 2026 11:23:47 +0200 [thread overview]
Message-ID: <20261109092347.3975686-1-mkashani@nvidia.com> (raw)
Representor matching is always enabled on an E-Switch port, and the PMD
reserves egress group 0 for the default SQ tagging rule. Removing
repr_matching_en left the user group shift enabled only for extended
metadata mode. With any other dv_xmeta_en value, an external egress
group 0 rule is installed on the root table, where a jump to a non-root
group matches but does not continue.
Shift every external egress group when the E-Switch is enabled.
This restores the previous repr_matching_en=1 behavior.
Fixes: c41f621786ff ("net/mlx5: remove representor matching devarg")
Cc: stable@dpdk.org
Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
---
drivers/net/mlx5/mlx5_flow_hw.c | 6 ++----
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/net/mlx5/mlx5_flow_hw.c b/drivers/net/mlx5/mlx5_flow_hw.c
index 8dabf21b768..4b30befa2d1 100644
--- a/drivers/net/mlx5/mlx5_flow_hw.c
+++ b/drivers/net/mlx5/mlx5_flow_hw.c
@@ -5591,7 +5591,6 @@ __translate_group(struct rte_eth_dev *dev,
"group index not supported");
*table_group = group + 1;
} else if (config->dv_esw_en &&
- config->dv_xmeta_en == MLX5_XMETA_MODE_META32_HWS &&
external &&
flow_attr->egress) {
/*
@@ -5600,9 +5599,8 @@ __translate_group(struct rte_eth_dev *dev,
* These flow rules are inserted in group 0 and this group is reserved by PMD
* for these purposes.
*
- * As a result, if representor matching or extended metadata mode is enabled,
- * group provided by the user must be incremented to avoid inserting flow rules
- * in group 0.
+ * Representor matching is always enabled, so the group provided by the user
+ * must be incremented to avoid inserting flow rules in group 0.
*/
if (group > MLX5_HW_MAX_EGRESS_GROUP)
return rte_flow_error_set(error, EINVAL,
--
2.25.1
next reply other threads:[~2026-11-09 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 9:23 Maayan Kashani [this message]
2026-11-11 13:10 ` [PATCH] net/mlx5: fix external egress group translation Raslan Darawsheh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261109092347.3975686-1-mkashani@nvidia.com \
--to=mkashani@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=viacheslavo@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox