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>
Cc: dev@dpdk.org, Erez Shitrit <erezsh@nvidia.com>
Subject: Re: [PATCH] net/mlx5: fix mark action creation
Date: Sun, 31 Aug 2025 15:19:11 +0300 [thread overview]
Message-ID: <cab3bd69-c338-4d3f-bb39-009507f57b95@nvidia.com> (raw)
In-Reply-To: <20250814132411.799853-1-dsosnowski@nvidia.com>
Hi,
On 14/08/2025 4:24 PM, Dariusz Sosnowski wrote:
> Mark flow action is implemented using a flow tag action
> exposed by HWS layer.
> Whenever flow tag action is used in FDB domain,
> HWS layer has to create relevant STC for both FDB sides,
> i.e., FDB_RX and FDB_TX.
> Flow tag action is not supported on FDB_TX.
>
> This patch adds missing STC fixup code when FDB domain is used,
> so that on FDB_TX side, NOP action is used in place of flow tag.
>
> It also updates the higher level mlx5 PMD code to reject usage of mark
> flow action in actions templates with transfer attribute set,
> and prohibits creation of flow tag action on FDB
> if it is not supported by current FW.
>
> Fixes: 794b9b37922f ("net/mlx5: allow FDB RSS")
>
> Signed-off-by: Erez Shitrit <erezsh@nvidia.com>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Bing Zhao <bingz@nvidia.com>
> Acked-by: Suanming Mou <suanmingm@nvidia.com>
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-08-31 12:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:24 Dariusz Sosnowski
2025-08-31 12:19 ` 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=cab3bd69-c338-4d3f-bb39-009507f57b95@nvidia.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=erezsh@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--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).