From: Raslan Darawsheh <rasland@nvidia.com>
To: Bing Zhao <bingz@nvidia.com>, Matan Azrad <matan@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Michael Baum <michaelba@nvidia.com>
Subject: RE: [PATCH 1/7] net/mlx5: fix the modify field check of tag
Date: Mon, 10 Jul 2023 10:34:49 +0000 [thread overview]
Message-ID: <BYAPR12MB307894DCC33E4B684905403FCF30A@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20230630054303.432238-1-bingz@nvidia.com>
Hi,
> -----Original Message-----
> From: Bing Zhao <bingz@nvidia.com>
> Sent: Friday, June 30, 2023 8:43 AM
> To: Matan Azrad <matan@nvidia.com>; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>
> Cc: dev@dpdk.org; Michael Baum <michaelba@nvidia.com>
> Subject: [PATCH 1/7] net/mlx5: fix the modify field check of tag
>
> The new member "tag_index" was added into the structure
> "rte_flow_action_modify_data". It is the index of the header inside
> encapsulation level. Both the "RTE_FLOW_FIELD_TAG" and
> "MLX5_RTE_FLOW_FIELD_META_REG" types will use this member instead of
> the "level", but the "level" will still be supported for the compatibility.
>
> In the validation stage, not only the "RTE_FLOW_FIELD_TAG" type, but also
> the "MLX5_RTE_FLOW_FIELD_META_REG" needs to be checked.
>
> In the meanwhile, lowering down the log priority will help to prevent the
> flooding.
>
> Fixes: 68c513e861ca ("net/mlx5: align implementation with modify API")
> Cc: michaelba@nvidia.com
>
> Signed-off-by: Bing Zhao <bingz@nvidia.com>
> Acked-by: Ori Kam <orika@nvidia.com>
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2023-07-10 10:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 5:43 Bing Zhao
2023-06-30 6:08 ` Stephen Hemminger
2023-07-03 13:31 ` Bing Zhao
2023-07-06 9:37 ` Thomas Monjalon
2023-07-06 9:59 ` Bing Zhao
2023-07-10 10:34 ` 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=BYAPR12MB307894DCC33E4B684905403FCF30A@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=michaelba@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).