From: Luca Boccassi <luca.boccassi@gmail.com>
To: Shani Peretz <shperetz@nvidia.com>
Cc: stable@dpdk.org, Dariusz Sosnowski <dsosnowski@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
Bing Zhao <bingz@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>,
Michael Baum <michaelba@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 22.11] net/mlx5: fix Tx metadata pattern template mismatch
Date: Thu, 20 Nov 2025 12:41:28 +0000 [thread overview]
Message-ID: <CAMw=ZnQ0himh+NQp+jvSr2_PQc+v0XvU=S2qg8c2zz2g2kG8Yw@mail.gmail.com> (raw)
In-Reply-To: <20251120104823.50618-1-shperetz@nvidia.com>
On Thu, 20 Nov 2025 at 10:48, Shani Peretz <shperetz@nvidia.com> wrote:
>
> When representor matching is disabled with dv_xmeta_en=4, the Tx metadata
> copy flows use SQ (send queue) pattern matching, but the pattern template
> was still configured to use ETH match-all pattern. This mismatch causes
> hardware to reject the flows with error CQEs during port configuration.
>
> This patch fixes the issue by using SQ-based pattern template
> (flow_hw_create_tx_repr_sq_pattern_tmpl) instead of the ETH match-all
> template (flow_hw_create_tx_default_mreg_copy_pattern_template).
>
> Fixes: 593fb3fdfa10 ("net/mlx5: fix multi process Tx default rules")
>
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> ---
> drivers/net/mlx5/mlx5_flow_hw.c | 42 +--------------------------------
> 1 file changed, 1 insertion(+), 41 deletions(-)
Hi, thanks for the patch, unfortunately this does not apply, neither
on https://git.dpdk.org/dpdk-stable/log/?h=22.11 nor on
https://github.com/bluca/dpdk-stable/tree/22.11
How was this tested?
next prev parent reply other threads:[~2025-11-20 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-20 10:48 Shani Peretz
2025-11-20 12:41 ` Luca Boccassi [this message]
2025-11-20 18:46 ` Shani Peretz
2025-11-20 18:45 ` [PATCH 22.11 v2] " Shani Peretz
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='CAMw=ZnQ0himh+NQp+jvSr2_PQc+v0XvU=S2qg8c2zz2g2kG8Yw@mail.gmail.com' \
--to=luca.boccassi@gmail.com \
--cc=bingz@nvidia.com \
--cc=dsosnowski@nvidia.com \
--cc=matan@nvidia.com \
--cc=michaelba@nvidia.com \
--cc=orika@nvidia.com \
--cc=shperetz@nvidia.com \
--cc=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--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;
as well as URLs for NNTP newsgroup(s).