From: Li Zhang <lizh@nvidia.com>
To: dekelp@nvidia.com, orika@nvidia.com, viacheslavo@nvidia.com,
matan@nvidia.com, shahafs@nvidia.com,
cristian.dumitrescu@intel.com, lironh@marvell.com
Cc: dev@dpdk.org, thomas@monjalon.net, rasland@nvidia.com, roniba@nvidia.com
Subject: [dpdk-dev] [PATCH 0/2] Support meter policy API
Date: Thu, 1 Apr 2021 09:54:45 +0300 [thread overview]
Message-ID: <20210401065448.1480127-1-lizh@nvidia.com> (raw)
Currently, the flow meter policy does not support multiple actions
per color; also the allowed action types per color are very limited.
In addition, the policy cannot be pre-defined.
Due to the growing in flow actions offload abilities there is a potential
for the user to use variety of actions per color differently.
This new meter policy API comes to allow this potential in the most ethdev
common way using rte_flow action definition.
A list of rte_flow actions will be provided by the user per color
in order to create a meter policy.
In addition, the API forces to pre-define the policy before
the meters creation in order to allow sharing of single policy
with multiple meters efficiently.
meter_policy_id is added into struct rte_mtr_params.
So that it can get the policy during the meters creation.
RFC ("ethdev: add pre-defined meter policy API")
https://patchwork.dpdk.org/project/dpdk/patch/20210318085815.804896-1-lizh@nvidia.com/
Haifei Luo (1):
app/testpmd: support policy actions per color
Li Zhang (1):
ethdev: add pre-defined meter policy API
app/test-flow-perf/main.c | 7 -
app/test-pmd/cmdline.c | 7 +-
app/test-pmd/cmdline_flow.c | 118 ++++-
app/test-pmd/cmdline_mtr.c | 257 +++-------
app/test-pmd/cmdline_mtr.h | 4 +-
app/test-pmd/config.c | 34 ++
app/test-pmd/testpmd.h | 2 +
doc/guides/rel_notes/release_20_11.rst | 3 +
drivers/net/mlx5/mlx5.h | 24 +-
drivers/net/mlx5/mlx5_flow.c | 46 --
drivers/net/mlx5/mlx5_flow.h | 18 +-
drivers/net/mlx5/mlx5_flow_aso.c | 8 +-
drivers/net/mlx5/mlx5_flow_dv.c | 461 +-----------------
drivers/net/mlx5/mlx5_flow_meter.c | 369 +-------------
drivers/net/softnic/rte_eth_softnic_flow.c | 19 +-
.../net/softnic/rte_eth_softnic_internals.h | 18 +-
drivers/net/softnic/rte_eth_softnic_meter.c | 303 +++++++++---
lib/librte_ethdev/rte_flow.h | 18 +
lib/librte_ethdev/rte_mtr.c | 55 ++-
lib/librte_ethdev/rte_mtr.h | 166 +++++--
lib/librte_ethdev/rte_mtr_driver.h | 44 +-
lib/librte_ethdev/version.map | 4 +
22 files changed, 747 insertions(+), 1238 deletions(-)
--
2.27.0
next reply other threads:[~2021-04-01 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 6:54 Li Zhang [this message]
2021-04-01 6:54 ` [dpdk-dev] [PATCH 1/2] ethdev: add pre-defined " Li Zhang
2021-04-01 6:54 ` [dpdk-dev] [PATCH 2/2] app/testpmd: support policy actions per color Li Zhang
2021-04-02 10:36 ` [dpdk-dev] [PATCH v2 0/2] Support meter policy API Li Zhang
2021-04-02 10:36 ` [dpdk-dev] [PATCH v2 1/2] ethdev: add pre-defined " Li Zhang
2021-04-08 13:55 ` Ori Kam
2021-04-08 14:37 ` Li Zhang
2021-04-02 10:36 ` [dpdk-dev] [PATCH v2 2/2] app/testpmd: support policy actions per color Li Zhang
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=20210401065448.1480127-1-lizh@nvidia.com \
--to=lizh@nvidia.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dekelp@nvidia.com \
--cc=dev@dpdk.org \
--cc=lironh@marvell.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@nvidia.com \
--cc=roniba@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=thomas@monjalon.net \
--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).