From: Raslan Darawsheh <rasland@nvidia.com>
To: 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>,
Itamar Gozlan <igozlan@nvidia.com>
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5: fix higher flow tag indexes support on root
Date: Tue, 18 Nov 2025 13:23:44 +0200 [thread overview]
Message-ID: <0400d002-fcf1-4ca0-8f5e-872317e8ab67@nvidia.com> (raw)
In-Reply-To: <20251114201720.1639238-1-dsosnowski@nvidia.com>
Hi,
On 14/11/2025 10:17 PM, Dariusz Sosnowski wrote:
> Offending patch introduced support for additional flow tag indexes
> with HW Steering flow engine. New tag indexes will be mapped
> to HW registers REG_C_8 to REG_C_11, depending on HW capabilities.
>
> That patch only handled tables created on group > 0 (non-root table),
> where mlx5 PMD directly configures the HW.
> Tables and flow rules on group 0 (root table) are handled through
> kernel driver, and new registers were not addressed for that case.
>
> Because of that, usage of unsupported tag index in group 0
> triggered an assertion in flow_dv_match_meta_reg().
>
> This patch adds necessary definitions for REG_C_8 to REG_C_11 to make
> these registers usable for flow tag indexes in root table.
> Validation of flow tag to HW register translation is also amended
> to report invalid cases to the user, instead of relying on assertions.
>
> Fixes: 7e3a14423c1a ("net/mlx5/hws: support 4 additional C registers")
> Cc: igozlan@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-11-18 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 20:17 Dariusz Sosnowski
2025-11-18 7:44 ` Bing Zhao
2025-11-18 9:49 ` Dariusz Sosnowski
2025-11-18 9:51 ` Bing Zhao
2025-11-18 11:23 ` Raslan Darawsheh [this message]
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=0400d002-fcf1-4ca0-8f5e-872317e8ab67@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=igozlan@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;
as well as URLs for NNTP newsgroup(s).