From: Raslan Darawsheh <rasland@nvidia.com>
To: "Jiawei(Jonny) Wang" <jiaweiw@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>,
Suanming Mou <suanmingm@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: RE: [PATCH v2] net/mlx5: fix modify action attributes detection
Date: Mon, 5 Sep 2022 09:24:13 +0000 [thread overview]
Message-ID: <BYAPR12MB3078977A53A804333F67E449CF7F9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220901021156.15920-1-jiaweiw@nvidia.com>
Hi,
> -----Original Message-----
> From: Jiawei(Jonny) Wang <jiaweiw@nvidia.com>
> Sent: Thursday, September 1, 2022 5:12 AM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Ori Kam <orika@nvidia.com>; Suanming Mou
> <suanmingm@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>;
> stable@dpdk.org
> Subject: [PATCH v2] net/mlx5: fix modify action attributes detection
>
> The driver splits the flow with sample action into two sub-flows,
> sub prefix flow and sub suffix flow.
>
> In the case of tunnel flow including a decap action, the driver should
> translate the inner as outer for actions coming after the decap action.
> In the case of flow splitting, the packet layers, used to detect the
> attributes, are inherited from the prefix flow to the suffix flow but
> the driver wrongly didn't handle the decap adjustment and the inner
> layers didn't shift to the outer.
>
> This patch adjusts the inherited layers in case of decap.
>
> Fixes: 6e77151286b2 ("net/mlx5: fix match information in meter")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jiawei Wang <jiaweiw@nvidia.com>
> Acked-by: Matan Azrad <matan@nvidia.com>
> ---
> v2: fix the style warning
> ---
Patch applied to next-net-mlx,
Concerning this failure:
http://mails.dpdk.org/archives/test-report/2022-September/304146.html
Please note to send always in reply to your previous version,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-09-05 9:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 2:11 Jiawei Wang
2022-09-05 9:24 ` 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=BYAPR12MB3078977A53A804333F67E449CF7F9@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=jiaweiw@nvidia.com \
--cc=matan@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).