From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: <dev@dpdk.org>
Cc: David Marchand <david.marchand@redhat.com>
Subject: [dpdk-dev] [PATCH 0/4] net/mlx5: keep indirect actions across port restart
Date: Tue, 27 Jul 2021 10:31:16 +0300 [thread overview]
Message-ID: <20210727073121.895620-1-dkozlyuk@nvidia.com> (raw)
It was unspecified what happens to indirect actions when a port
is stopped, possibly reconfigured, and started again. MLX5 PMD,
the first one to use indirect actions, intended to keep them across
such a sequence, but the implementation was buggy. Patches 1-3 fix
the PMD behavior, patch 4 adds common specification with rationale.
Dmitry Kozlyuk (4):
net/mlx5: discover max flow priority using DevX
net/mlx5: create drop queue using DevX
net/mlx5: preserve indirect actions across port restart
ethdev: document indirect flow action life cycle
doc/guides/prog_guide/rte_flow.rst | 10 +
drivers/net/mlx5/linux/mlx5_os.c | 5 -
drivers/net/mlx5/mlx5_devx.c | 204 +++++++++++++++++---
drivers/net/mlx5/mlx5_flow.c | 292 ++++++++++++++++++++++++++---
drivers/net/mlx5/mlx5_flow.h | 6 +
drivers/net/mlx5/mlx5_flow_dv.c | 103 ++++++++++
drivers/net/mlx5/mlx5_flow_verbs.c | 77 +-------
drivers/net/mlx5/mlx5_rx.h | 4 +
drivers/net/mlx5/mlx5_rxq.c | 99 ++++++++--
drivers/net/mlx5/mlx5_trigger.c | 10 +
lib/ethdev/rte_flow.h | 4 +
11 files changed, 680 insertions(+), 134 deletions(-)
--
2.25.1
next reply other threads:[~2021-07-27 7:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 7:31 Dmitry Kozlyuk [this message]
2021-07-27 7:31 ` [dpdk-dev] [PATCH 1/4] net/mlx5: discover max flow priority using DevX Dmitry Kozlyuk
2021-07-27 7:31 ` [dpdk-dev] [PATCH 2/4] net/mlx5: create drop queue " Dmitry Kozlyuk
2021-07-27 7:31 ` [dpdk-dev] [PATCH 3/4] net/mlx5: preserve indirect actions across port restart Dmitry Kozlyuk
2021-07-27 7:31 ` [dpdk-dev] [PATCH 4/4] ethdev: document indirect flow action life cycle Dmitry Kozlyuk
2021-07-28 9:50 ` Ori Kam
2021-07-28 8:05 ` [dpdk-dev] [PATCH 0/4] net/mlx5: keep indirect actions across port restart Andrew Rybchenko
2021-07-28 11:18 ` Dmitry Kozlyuk
2021-07-28 12:07 ` Ori Kam
2021-07-28 12:26 ` Andrew Rybchenko
2021-07-28 14:08 ` Dmitry Kozlyuk
2021-07-28 17:07 ` Ori Kam
2021-07-29 14:00 ` [dpdk-dev] [PATCH v2 " Dmitry Kozlyuk
2021-07-29 14:00 ` [dpdk-dev] [PATCH v2 1/3] net/mlx5: discover max flow priority using DevX Dmitry Kozlyuk
2021-07-29 14:00 ` [dpdk-dev] [PATCH v2 2/3] net/mlx5: create drop queue " Dmitry Kozlyuk
2021-07-29 14:00 ` [dpdk-dev] [PATCH v2 3/3] net/mlx5: preserve indirect actions across port restart Dmitry Kozlyuk
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=20210727073121.895620-1-dkozlyuk@nvidia.com \
--to=dkozlyuk@nvidia.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).