From: Patrick Robb <probb@iol.unh.edu>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>
Cc: 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>, Alex Vesker <valex@nvidia.com>,
Erez Shitrit <erezsh@nvidia.com>,
dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH] net/mlx5/hws: fix TIR action support in FDB
Date: Fri, 15 Aug 2025 11:21:51 -0400 [thread overview]
Message-ID: <CAJvnSUDdAZ4w8BtoVnz_ZbSdBh96s7TWCsx+KjAS_OywHf3tHg@mail.gmail.com> (raw)
In-Reply-To: <20250814132002.799724-1-dsosnowski@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1452 bytes --]
Sending a CI testing retest for this series because of a suspected false
failure on the packet capture testsuite.
On Thu, Aug 14, 2025 at 9:22 AM Dariusz Sosnowski <dsosnowski@nvidia.com>
wrote:
> TIR action was not added as an allowed action in FDB domain.
> This prevented the usage of RSS flow action in transfer flow rules
> with HW Steering flow engine.
>
> Fixes: 1f8fc88d4d31 ("net/mlx5/hws: allow jump to TIR over FDB")
> Cc: valex@nvidia.com
> Cc: stable@dpdk.org
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Acked-by: Bing Zhao <bingz@nvidia.com>
> Acked-by: Suanming Mou <suanmingm@nvidia.com>
> ---
> drivers/net/mlx5/hws/mlx5dr_action.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/net/mlx5/hws/mlx5dr_action.c
> b/drivers/net/mlx5/hws/mlx5dr_action.c
> index c1c6d28ac4..d765d57a8f 100644
> --- a/drivers/net/mlx5/hws/mlx5dr_action.c
> +++ b/drivers/net/mlx5/hws/mlx5dr_action.c
> @@ -94,6 +94,7 @@ static const uint32_t
> action_order_arr[MLX5DR_TABLE_TYPE_MAX][MLX5DR_ACTION_TYP_
> BIT(MLX5DR_ACTION_TYP_REFORMAT_L2_TO_TNL_L3),
> BIT(MLX5DR_ACTION_TYP_TBL) |
> BIT(MLX5DR_ACTION_TYP_MISS) |
> + BIT(MLX5DR_ACTION_TYP_TIR) |
> BIT(MLX5DR_ACTION_TYP_VPORT) |
> BIT(MLX5DR_ACTION_TYP_DROP) |
> BIT(MLX5DR_ACTION_TYP_DEST_ROOT) |
> --
> 2.39.5
>
>
[-- Attachment #2: Type: text/html, Size: 2169 bytes --]
prev parent reply other threads:[~2025-08-15 15:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 13:20 Dariusz Sosnowski
2025-08-15 15:21 ` Patrick Robb [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=CAJvnSUDdAZ4w8BtoVnz_ZbSdBh96s7TWCsx+KjAS_OywHf3tHg@mail.gmail.com \
--to=probb@iol.unh.edu \
--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=stable@dpdk.org \
--cc=suanmingm@nvidia.com \
--cc=valex@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).