From: Raslan Darawsheh <rasland@nvidia.com>
To: Shun Hao <shunh@nvidia.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Matan Azrad <matan@nvidia.com>, Ori Kam <orika@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v1 0/2] Fix meter flow fail when matching E-Switch Manager
Date: Mon, 20 Jun 2022 07:22:03 +0000 [thread overview]
Message-ID: <BYAPR12MB3078EFDC3553F1BB60984630CFB09@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220619032128.24588-1-shunh@nvidia.com>
Hi,
> -----Original Message-----
> From: Shun Hao <shunh@nvidia.com>
> Sent: Sunday, June 19, 2022 6:21 AM
> To: Slava Ovsiienko <viacheslavo@nvidia.com>; Matan Azrad
> <matan@nvidia.com>; Ori Kam <orika@nvidia.com>
> Cc: dev@dpdk.org; Raslan Darawsheh <rasland@nvidia.com>
> Subject: [PATCH v1 0/2] Fix meter flow fail when matching E-Switch Manager
>
> When using a meter in flow that matches E-Switch Manager, it will fail due to
> not handling E-Switch Manager match item correctly. This series fix this by
> using correct handling of parsing E-Switch Manager item.
>
> Shun Hao (2):
> net/mlx5: add limitation for E-Switch Manager match
> net/mlx5: fix meter fail when used on E-Switch Manager
>
> doc/guides/nics/mlx5.rst | 4 ++
> drivers/net/mlx5/mlx5_flow.c | 93 ++++++++++++++++++++++++++++----
> -
> drivers/net/mlx5/mlx5_flow.h | 10 ++++
> drivers/net/mlx5/mlx5_flow_dv.c | 42 +++------------
> 4 files changed, 100 insertions(+), 49 deletions(-)
>
> --
> 2.20.0
Series applied to next-net-mlx,
Kindest regards,
Raslan Darawsheh
prev parent reply other threads:[~2022-06-20 7:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 3:21 Shun Hao
2022-06-19 3:21 ` [PATCH v1 1/2] net/mlx5: add limitation for E-Switch Manager match Shun Hao
2022-06-19 3:21 ` [PATCH v1 2/2] net/mlx5: fix meter fail when used on E-Switch Manager Shun Hao
2022-06-20 7:22 ` 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=BYAPR12MB3078EFDC3553F1BB60984630CFB09@BYAPR12MB3078.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=shunh@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).