From: Raslan Darawsheh <rasland@nvidia.com>
To: Maayan Kashani <mkashani@nvidia.com>, dev@dpdk.org
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>,
Alexander Kozyrev <akozyrev@nvidia.com>
Subject: Re: [PATCH] net/mlx5: fix modify field action operation restriction
Date: Thu, 6 Nov 2025 16:04:21 +0200 [thread overview]
Message-ID: <2265f1a4-4ffb-4454-9818-e019d78f31d6@nvidia.com> (raw)
In-Reply-To: <20251105085049.110213-1-mkashani@nvidia.com>
Hi,
On 05/11/2025 10:50 AM, Maayan Kashani wrote:
> Update DV flow engine modify field validation:
> - Reject 'add' and 'sub' operations when source field is not VALUE
> or POINTER in DV flow engine.
>
> Update documentation to clarify operation support:
> - 'set' operation is supported in all modes
> - 'add' operation with VALUE/POINTER source fields is
> supported in DV/HWS mode.
> - Specify relevant HW supporting packet header as 'src' field.
> - List supported 'dst' fields.
>
> Fixes: 641dbe4fb053 ("net/mlx5: support modify field flow action")
> Cc: stable@dpdk.org
>
> Signed-off-by: Maayan Kashani <mkashani@nvidia.com>
> Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
>
> #. In template tables of group 0, the modify action must be fully masked.
>
> diff --git a/drivers/net/mlx5/mlx5_flow_dv.c b/drivers/net/mlx5/mlx5_flow_dv.c
> index f765f941162..95ca57e8c46 100644
> --- a/drivers/net/mlx5/mlx5_flow_dv.c
> +++ b/drivers/net/mlx5/mlx5_flow_dv.c
> @@ -5642,6 +5642,13 @@ flow_dv_validate_action_modify_field(struct rte_eth_dev *dev,
> }
> if (src_data->field != RTE_FLOW_FIELD_VALUE &&
> src_data->field != RTE_FLOW_FIELD_POINTER) {
> + if (conf->operation != RTE_FLOW_MODIFY_SET)
> + return rte_flow_error_set(error, ENOTSUP,
> + RTE_FLOW_ERROR_TYPE_ACTION_CONF,
> + &conf->operation,
> + "modify field action type add is not"
> + " supported when src field type is"
> + " not value/pointer");
> if (root)
> return rte_flow_error_set(error, ENOTSUP,
> RTE_FLOW_ERROR_TYPE_ACTION, action,
Patch applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2025-11-06 14:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-05 8:50 Maayan Kashani
2025-11-06 14:04 ` 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=2265f1a4-4ffb-4454-9818-e019d78f31d6@nvidia.com \
--to=rasland@nvidia.com \
--cc=akozyrev@nvidia.com \
--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=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).