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/3] Fix meter hierarchy issue for represented port
Date: Wed, 21 Sep 2022 11:30:59 +0000 [thread overview]
Message-ID: <BYAPR12MB3078B8D009CCD0B28EC3EB73CF4F9@BYAPR12MB3078.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20220917060210.3332529-1-shunh@nvidia.com>
Hi,
> -----Original Message-----
> From: Shun Hao <shunh@nvidia.com>
> Sent: Saturday, September 17, 2022 9:02 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/3] Fix meter hierarchy issue for represented port
>
> When the represented port item was introduced, there's an issue that if a
> flow matching represented port item uses a meter hierarchy action, it will fail
> due to the represented port item not supported correctly in meter hierarchy
> creation.
>
> This patch set is adding the correct handling to support represented port.
> And there're some limitation for the support that when matching all ports,
> the meter hierarchy should not contain any meter having drop count.
>
> Shun Hao (3):
> net/mlx5: fix meter hierarchy with represented port item
> net/mlx5: add meter flow limitation when matching all ports
> net/mlx5: fix meter ID tag for meter hierarchy
>
> doc/guides/nics/mlx5.rst | 1 +
> drivers/net/mlx5/mlx5.h | 2 +
> drivers/net/mlx5/mlx5_flow.c | 27 +++++++++----
> drivers/net/mlx5/mlx5_flow.h | 4 ++
> drivers/net/mlx5/mlx5_flow_dv.c | 71 ++++++++++++++++++++++----------
> -
> 5 files changed, 73 insertions(+), 32 deletions(-)
>
> --
> 2.20.0
Series applied to next-net-mlx,
Kindest regards
Raslan Darawsheh
prev parent reply other threads:[~2022-09-21 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 6:02 Shun Hao
2022-09-17 6:02 ` [PATCH v1 1/3] net/mlx5: fix meter hierarchy with represented port item Shun Hao
2022-09-17 6:02 ` [PATCH v1 2/3] net/mlx5: add meter flow limitation when matching all ports Shun Hao
2022-09-17 6:02 ` [PATCH v1 3/3] net/mlx5: fix meter ID tag for meter hierarchy Shun Hao
2022-09-21 11:30 ` 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=BYAPR12MB3078B8D009CCD0B28EC3EB73CF4F9@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).