From: Michael Baum <michaelba@nvidia.com>
To: <dev@dpdk.org>
Cc: Matan Azrad <matan@nvidia.com>,
Raslan Darawsheh <rasland@nvidia.com>,
"Ori Kam" <orika@nvidia.com>
Subject: [PATCH 0/3] ethdev: AGE action preparation
Date: Wed, 21 Sep 2022 17:54:06 +0300 [thread overview]
Message-ID: <20220921145409.511328-1-michaelba@nvidia.com> (raw)
RFC's:
https://patchwork.dpdk.org/project/dpdk/patch/7a45693f478b1b721b4e05131141b526185a175c.1654063912.git.jackmin@nvidia.com/
https://patchwork.dpdk.org/project/dpdk/patch/608febf8d5d3c434a1eddb2e56f425ebbd6ff0b4.1654063912.git.jackmin@nvidia.com/
Michael Baum (3):
ethdev: add strict queue to pre-configuration flow hints
ethdev: add queue-based API to report aged flow rules
ethdev: add structure for indirect AGE update
app/test-pmd/cmdline_flow.c | 93 +++++++++-
app/test-pmd/config.c | 177 +++++++++++++++++++-
app/test-pmd/testpmd.h | 1 +
doc/guides/prog_guide/rte_flow.rst | 25 ++-
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 90 +++++++++-
lib/ethdev/rte_flow.c | 22 +++
lib/ethdev/rte_flow.h | 89 +++++++++-
lib/ethdev/rte_flow_driver.h | 7 +
lib/ethdev/version.map | 3 +
9 files changed, 491 insertions(+), 16 deletions(-)
--
2.25.1
next reply other threads:[~2022-09-21 14:54 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 14:54 Michael Baum [this message]
2022-09-21 14:54 ` [PATCH 1/3] ethdev: add strict queue to pre-configuration flow hints Michael Baum
2022-09-29 12:04 ` Ori Kam
2022-09-21 14:54 ` [PATCH 2/3] ethdev: add queue-based API to report aged flow rules Michael Baum
2022-09-29 12:04 ` Ori Kam
2022-09-21 14:54 ` [PATCH 3/3] ethdev: add structure for indirect AGE update Michael Baum
2022-09-29 12:39 ` Ori Kam
2022-10-03 8:03 ` Andrew Rybchenko
2022-10-03 8:30 ` Ori Kam
2022-10-03 13:17 ` Andrew Rybchenko
2022-10-03 15:13 ` Ori Kam
2022-10-04 6:36 ` Andrew Rybchenko
2022-10-19 13:09 ` Michael Baum
2022-09-29 8:40 ` [PATCH 0/3] ethdev: AGE action preparation Andrew Rybchenko
2022-10-19 13:12 ` [PATCH v2 " Michael Baum
2022-10-19 13:12 ` [PATCH v2 1/3] ethdev: add strict queue to pre-configuration flow hints Michael Baum
2022-10-19 13:12 ` [PATCH v2 2/3] ethdev: add queue-based API to report aged flow rules Michael Baum
2022-10-19 13:12 ` [PATCH v2 3/3] ethdev: add structure for indirect AGE update Michael Baum
2022-10-19 14:49 ` [PATCH v3 0/3] ethdev: AGE action preparation Michael Baum
2022-10-19 14:49 ` [PATCH v3 1/3] ethdev: add strict queue to pre-configuration flow hints Michael Baum
2022-10-26 19:10 ` Andrew Rybchenko
2022-10-19 14:49 ` [PATCH v3 2/3] ethdev: add queue-based API to report aged flow rules Michael Baum
2022-10-26 19:15 ` Andrew Rybchenko
2022-10-26 21:17 ` Michael Baum
2022-10-19 14:49 ` [PATCH v3 3/3] ethdev: add structure for indirect AGE update Michael Baum
2022-10-26 19:18 ` Andrew Rybchenko
2022-10-26 21:19 ` Michael Baum
2022-10-26 21:49 ` [PATCH v4 0/3] ethdev: AGE action preparation Michael Baum
2022-10-26 21:49 ` [PATCH v4 1/3] ethdev: add strict queue to pre-configuration flow hints Michael Baum
2022-10-26 21:49 ` [PATCH v4 2/3] ethdev: add queue-based API to report aged flow rules Michael Baum
2022-10-26 21:49 ` [PATCH v4 3/3] ethdev: add structure for indirect AGE update Michael Baum
2022-10-28 10:56 ` [PATCH v4 0/3] ethdev: AGE action preparation Andrew Rybchenko
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=20220921145409.511328-1-michaelba@nvidia.com \
--to=michaelba@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=rasland@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).