From: Alexander Kozyrev <akozyrev@nvidia.com>
To: <dev@dpdk.org>
Cc: <orika@nvidia.com>, <thomas@monjalon.net>,
<ivan.malov@oktetlabs.ru>, <andrew.rybchenko@oktetlabs.ru>,
<ferruh.yigit@intel.com>, <mohammad.abdul.awal@intel.com>,
<qi.z.zhang@intel.com>, <jerinj@marvell.com>,
<ajit.khaparde@broadcom.com>
Subject: [PATCH 00/10] ethdev: datapath-focused flow rules management
Date: Tue, 18 Jan 2022 07:02:11 +0200 [thread overview]
Message-ID: <20220118050221.3914960-1-akozyrev@nvidia.com> (raw)
Three major changes to a generic RTE Flow API were implemented in order
to speed up flow rule insertion/destruction and adapt the API to the
needs of a datapath-focused flow rules management applications:
1. Pre-configuration hints.
Application may give us some hints on what type of resources are needed.
Introduce the configuration routine to prepare all the needed resources
inside a PMD/HW before any flow rules are created at the init stage.
2. Flow grouping using templates.
Use the knowledge about which flow rules are to be used in an application
and prepare item and action templates for them in advance. Group flow rules
with common patterns and actions together for better resource management.
3. Queue-based flow management.
Perform flow rule insertion/destruction asynchronously to spare the datapath
from blocking on RTE Flow API and allow it to continue with packet processing.
Enqueue flow rules operations and poll for the results later.
testpmd examples are part of the patch series. PMD changes will follow.
RFC: https://patchwork.dpdk.org/project/dpdk/cover/20211006044835.3936226-1-akozyrev@nvidia.com/
Signed-off-by: Alexander Kozyrev <akozyrev@nvidia.com>
Alexander Kozyrev (10):
ethdev: introduce flow pre-configuration hints
ethdev: add flow item/action templates
ethdev: bring in async queue-based flow rules operations
app/testpmd: implement rte flow configure
app/testpmd: implement rte flow item/action template
app/testpmd: implement rte flow table
app/testpmd: implement rte flow queue create flow
app/testpmd: implement rte flow queue drain
app/testpmd: implement rte flow queue dequeue
app/testpmd: implement rte flow queue indirect action
app/test-pmd/cmdline_flow.c | 1484 ++++++++++++++++-
app/test-pmd/config.c | 731 ++++++++
app/test-pmd/testpmd.h | 61 +
doc/guides/prog_guide/img/rte_flow_q_init.svg | 71 +
.../prog_guide/img/rte_flow_q_usage.svg | 60 +
doc/guides/prog_guide/rte_flow.rst | 319 ++++
doc/guides/rel_notes/release_22_03.rst | 19 +
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 350 +++-
lib/ethdev/rte_flow.c | 332 ++++
lib/ethdev/rte_flow.h | 680 ++++++++
lib/ethdev/rte_flow_driver.h | 103 ++
lib/ethdev/version.map | 16 +
12 files changed, 4203 insertions(+), 23 deletions(-)
create mode 100644 doc/guides/prog_guide/img/rte_flow_q_init.svg
create mode 100644 doc/guides/prog_guide/img/rte_flow_q_usage.svg
--
2.18.2
next reply other threads:[~2022-01-18 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-18 5:02 Alexander Kozyrev [this message]
2022-01-18 5:02 ` [PATCH 01/10] ethdev: introduce flow pre-configuration hints Alexander Kozyrev
2022-01-18 5:02 ` [PATCH 02/10] ethdev: add flow item/action templates Alexander Kozyrev
2022-01-18 5:02 ` [PATCH 03/10] ethdev: bring in async queue-based flow rules operations Alexander Kozyrev
2022-01-18 5:02 ` [PATCH 04/10] app/testpmd: implement rte flow configure Alexander Kozyrev
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=20220118050221.3914960-1-akozyrev@nvidia.com \
--to=akozyrev@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=ivan.malov@oktetlabs.ru \
--cc=jerinj@marvell.com \
--cc=mohammad.abdul.awal@intel.com \
--cc=orika@nvidia.com \
--cc=qi.z.zhang@intel.com \
--cc=thomas@monjalon.net \
/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).