From: Dmitry Kozlyuk <dkozlyuk@nvidia.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] [RFC PATCH 0/2] Flow entities behavior across port restart
Date: Wed, 1 Sep 2021 11:55:14 +0300 [thread overview]
Message-ID: <20210901085516.3647814-1-dkozlyuk@nvidia.com> (raw)
It is currently unspecified if flow rules and indirect actions persist
across port restart and reconfiguration. Actual behavior differs between
PMDs, for example, i40e and mlx5. There are patches that try to fix
particular behavior [1] or at least document it for specific PMDs [2].
We propose to codify the least demanding behavior, i.e. no persistence,
and to add device capabilities for persistence of rules and actions.
This continues the discussion thread [3].
[1]: http://patchwork.dpdk.org/project/dpdk/list/?series=18065
[2]: http://patchwork.dpdk.org/project/dpdk/list/?series=17939
[3]: http://inbox.dpdk.org/dev/20210727073121.895620-5-dkozlyuk@nvidia.com/
Dmitry Kozlyuk (2):
ethdev: add capability to keep flow rules on restart
ethdev: add capability to keep indirect actions on restart
doc/guides/prog_guide/rte_flow.rst | 21 +++++++++++++++++++++
lib/ethdev/rte_ethdev.h | 7 +++++++
2 files changed, 28 insertions(+)
--
2.25.1
next reply other threads:[~2021-09-01 8:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 8:55 Dmitry Kozlyuk [this message]
2021-09-01 8:55 ` [dpdk-dev] [RFC PATCH 1/2] ethdev: add capability to keep flow rules on restart Dmitry Kozlyuk
2021-09-01 8:55 ` [dpdk-dev] [RFC PATCH 2/2] ethdev: add capability to keep indirect actions " Dmitry Kozlyuk
2021-09-27 11:21 ` Dmitry Kozlyuk
2021-10-06 17:12 ` Ajit Khaparde
2021-10-07 8:16 ` Dmitry Kozlyuk
2021-10-11 13:58 ` Andrew Rybchenko
2021-10-11 15:53 ` Ori Kam
2021-10-12 9:15 ` Andrew Rybchenko
2021-10-12 10:26 ` Ori Kam
2021-10-12 10:41 ` Andrew Rybchenko
2021-10-13 8:36 ` Dmitry Kozlyuk
2021-10-11 15:57 ` Dmitry Kozlyuk
2021-10-05 17:23 ` [dpdk-dev] [RFC PATCH 0/2] Flow entities behavior across port restart Thomas Monjalon
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=20210901085516.3647814-1-dkozlyuk@nvidia.com \
--to=dkozlyuk@nvidia.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).