From: Raslan Darawsheh <rasland@nvidia.com>
To: Gregory Etelson <getelson@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
"stable@dpdk.org" <stable@dpdk.org>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Dekel Peled <dekelp@nvidia.com>, Ori Kam <orika@nvidia.com>
Subject: RE: [PATCH] net/mlx5: fix IPv6 flow item validation for VERB API
Date: Tue, 8 Mar 2022 16:54:26 +0000 [thread overview]
Message-ID: <BYAPR12MB30786190F3F47E519C0867E7CF099@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <BYAPR12MB3078C90B31D6042DE75ECE2ACF099@BYAPR12MB3078.namprd12.prod.outlook.com>
Hi,
> -----Original Message-----
> From: Raslan Darawsheh
> Sent: Tuesday, March 8, 2022 11:10 AM
> To: Gregory Etelson <getelson@nvidia.com>; dev@dpdk.org
> Cc: Matan Azrad <matan@nvidia.com>; stable@dpdk.org; Slava Ovsiienko
> <viacheslavo@nvidia.com>; Dekel Peled <dekelp@nvidia.com>; Ori Kam
> <orika@nvidia.com>
> Subject: RE: [PATCH] net/mlx5: fix IPv6 flow item validation for VERB API
>
> Hi,
>
> > -----Original Message-----
> > From: Gregory Etelson <getelson@nvidia.com>
> > Sent: Monday, March 7, 2022 7:18 PM
> > To: dev@dpdk.org
> > Cc: Gregory Etelson <getelson@nvidia.com>; Matan Azrad
> > <matan@nvidia.com>; Raslan Darawsheh <rasland@nvidia.com>;
> > stable@dpdk.org; Slava Ovsiienko <viacheslavo@nvidia.com>; Dekel Peled
> > <dekelp@nvidia.com>; Ori Kam <orika@nvidia.com>
> > Subject: [PATCH] net/mlx5: fix IPv6 flow item validation for VERB API
> >
> > In case the PMD was activated over VERB API, limit IPv6 flow item next
> > protocol mask value to 0 or 0xFF.
> > The limitation is required for RSS flow action TCP and UDP types.
> >
> > Cc: stable@dpdk.org
> >
> > Fixes: 491757372f98 ("net/mlx5: enforce limitation on IPv6 next
> > protocol")
> > Signed-off-by: Gregory Etelson <getelson@nvidia.com>
> > Acked-by: Matan Azrad <matan@nvidia.com>
>
> Patch applied to next-net-mlx,
>
> Kindest regards,
> Raslan Darawsheh
Dropping this patch from next-net-mlx as it introduces a new bug with dv_flow_en,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-03-08 16:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 17:17 Gregory Etelson
2022-03-08 9:09 ` Raslan Darawsheh
2022-03-08 16:54 ` 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=BYAPR12MB30786190F3F47E519C0867E7CF099@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dekelp@nvidia.com \
--cc=dev@dpdk.org \
--cc=getelson@nvidia.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=stable@dpdk.org \
--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).