From: Shun Hao <shunh@nvidia.com>
To: <viacheslavo@nvidia.com>, <matan@nvidia.com>, <orika@nvidia.com>
Cc: <dev@dpdk.org>, <rasland@nvidia.com>
Subject: [PATCH v1 0/3] Fix meter hierarchy issue for represented port
Date: Sat, 17 Sep 2022 09:02:07 +0300 [thread overview]
Message-ID: <20220917060210.3332529-1-shunh@nvidia.com> (raw)
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
next reply other threads:[~2022-09-17 6:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-17 6:02 Shun Hao [this message]
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 ` [PATCH v1 0/3] Fix meter hierarchy issue for represented port Raslan Darawsheh
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=20220917060210.3332529-1-shunh@nvidia.com \
--to=shunh@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@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).