DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ivan Malov <ivan.malov@arknetworks.am>
To: Maayan Kashani <mkashani@nvidia.com>
Cc: dev@dpdk.org, rasland@nvidia.com, 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>
Subject: Re: [PATCH] net/mlx5: fix unsupported port ID action
Date: Thu, 7 Aug 2025 15:44:20 +0400 (+04)	[thread overview]
Message-ID: <85f5793f-232b-ae04-7286-33e27dc83c6d@arknetworks.am> (raw)
In-Reply-To: <20250807091247.155266-1-mkashani@nvidia.com>

On Thu, 7 Aug 2025, Maayan Kashani wrote:

> When dv_flow_en=2, the port ID action is not supported.
> Although a rule can be created successfully in non-template mode,
> the specified action will be silently ignored and not applied.
>
> To prevent this ambiguous behavior, explicitly return an error
> when a port ID action is used with dv_flow_en=2,
> and recommend using a represented port action instead.
>
> Fixes: f1fecffa88df ("net/mlx5: support Direct Rules action template API")
> Cc: stable@dpdk.org
>
> Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>

Acked-by: Ivan Malov <ivan.malov@arknetworks.am>

> ---
> drivers/net/mlx5/mlx5_flow_hw.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/mlx5/mlx5_flow_hw.c b/drivers/net/mlx5/mlx5_flow_hw.c
> index 6dc16f80d32..58d4882cb96 100644
> --- a/drivers/net/mlx5/mlx5_flow_hw.c
> +++ b/drivers/net/mlx5/mlx5_flow_hw.c
> @@ -2913,6 +2913,10 @@ __flow_hw_translate_actions_template(struct rte_eth_dev *dev,
> 		case RTE_FLOW_ACTION_TYPE_END:
> 			actions_end = true;
> 			break;
> +		case RTE_FLOW_ACTION_TYPE_PORT_ID:
> +			DRV_LOG(ERR, "RTE_FLOW_ACTION_TYPE_PORT_ID action is not supported. "
> +				"Use RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT instead.");
> +			goto err;
> 		default:
> 			break;
> 		}
> @@ -7644,7 +7648,11 @@ flow_hw_parse_flow_actions_to_dr_actions(struct rte_eth_dev *dev,
> 		case MLX5_RTE_FLOW_ACTION_TYPE_MIRROR:
> 			at->dr_off[i] = curr_off;
> 			action_types[curr_off++] = MLX5DR_ACTION_TYP_DEST_ARRAY;
> -				break;
> +			break;
> +		case RTE_FLOW_ACTION_TYPE_PORT_ID:
> +			DRV_LOG(ERR, "RTE_FLOW_ACTION_TYPE_PORT_ID action is not supported. "
> +				"Use RTE_FLOW_ACTION_TYPE_REPRESENTED_PORT instead.");
> +			return -EINVAL;
> 		default:
> 			type = mlx5_hw_dr_action_types[at->actions[i].type];
> 			at->dr_off[i] = curr_off;
> -- 
> 2.21.0
>
>

      reply	other threads:[~2025-08-07 11:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-07  9:12 Maayan Kashani
2025-08-07 11:44 ` Ivan Malov [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=85f5793f-232b-ae04-7286-33e27dc83c6d@arknetworks.am \
    --to=ivan.malov@arknetworks.am \
    --cc=bingz@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dsosnowski@nvidia.com \
    --cc=matan@nvidia.com \
    --cc=mkashani@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=rasland@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).