From: Ivan Malov <ivan.malov@oktetlabs.ru>
To: dev@dpdk.org
Cc: Ori Kam <orika@nvidia.com>, Eli Britstein <elibr@nvidia.com>,
Ilya Maximets <i.maximets@ovn.org>,
Thomas Monjalon <thomas@monjalon.net>,
Stephen Hemminger <stephen@networkplumber.org>,
Jerin Jacob <jerinj@marvell.com>
Subject: [PATCH 00/13] ethdev: proceed with flow subsystem rework
Date: Fri, 12 Aug 2022 18:45:13 +0300 [thread overview]
Message-ID: <20220812154526.2681762-1-ivan.malov@oktetlabs.ru> (raw)
Series [1] requires that certain experimental flow features in DPDK
be promoted to stable. Also, reviewers request that some drivers be
adjusted to support flow action REPRESENTED_PORT. This series takes
care of that and also proceeds to remove deprecated items / actions.
Nevertheless, actions PF and VF are not removed for now since there
are PMDs which offer combined use of such actions with action QUEUE
in flow rules without attribute "transfer". Such problems will have
to be addressed either in v2 or in terms of a separate patch series.
The same goes for item / action PORT_ID. Will address it separately.
[1] http://patchwork.ozlabs.org/project/openvswitch/list/?series=310415
Ivan Malov (13):
ethdev: strip experimental tag off Rx metadata negotiate API
ethdev: strip experimental tag off port ID items and actions
ethdev: remove experimental tag from flow transfer proxy API
net/dpaa2: support represented port flow action
net/cnxk: support represented port flow action
app/testpmd: add port steering targets to sample flow action
doc: revisit outdated flow rule examples in testpmd tutorial
doc: add new port items and actions to switch representation
doc: rework VF-related explanations in switch representation
ethdev: remove deprecated flow item PF
ethdev: remove deprecated flow item VF
ethdev: remove deprecated flow item PHY PORT
ethdev: remove deprecated flow action PHY PORT
app/test-pmd/cmdline_flow.c | 107 +-
doc/guides/nics/cnxk.rst | 5 +
doc/guides/nics/features/bnxt.ini | 4 -
doc/guides/nics/features/cnxk.ini | 1 +
doc/guides/nics/features/cxgbe.ini | 4 -
doc/guides/nics/features/default.ini | 4 -
doc/guides/nics/features/dpaa2.ini | 2 +-
doc/guides/nics/features/i40e.ini | 1 -
doc/guides/nics/features/mlx5.ini | 1 -
doc/guides/nics/features/sfc.ini | 4 -
doc/guides/nics/sfc_efx.rst | 8 -
doc/guides/prog_guide/rte_flow.rst | 141 +--
.../prog_guide/switch_representation.rst | 223 ++--
doc/guides/rel_notes/release_22_11.rst | 38 +
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 63 +-
drivers/net/bnxt/bnxt_flow.c | 58 +-
drivers/net/bnxt/tf_ulp/ulp_rte_handler_tbl.c | 16 -
drivers/net/bnxt/tf_ulp/ulp_rte_parser.c | 183 ----
drivers/net/bnxt/tf_ulp/ulp_rte_parser.h | 20 -
drivers/net/cnxk/cnxk_flow.c | 9 +-
drivers/net/cxgbe/cxgbe_flow.c | 95 --
drivers/net/dpaa2/dpaa2_flow.c | 25 +-
drivers/net/i40e/i40e_flow.c | 987 ++----------------
drivers/net/sfc/sfc_mae.c | 230 ----
lib/ethdev/rte_ethdev.h | 4 -
lib/ethdev/rte_flow.c | 4 -
lib/ethdev/rte_flow.h | 155 ---
lib/ethdev/version.map | 4 +-
28 files changed, 316 insertions(+), 2080 deletions(-)
--
2.30.2
next reply other threads:[~2022-08-12 15:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 15:45 Ivan Malov [this message]
2022-08-12 19:18 Ivan Malov
2022-09-27 8:32 ` 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=20220812154526.2681762-1-ivan.malov@oktetlabs.ru \
--to=ivan.malov@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=elibr@nvidia.com \
--cc=i.maximets@ovn.org \
--cc=jerinj@marvell.com \
--cc=orika@nvidia.com \
--cc=stephen@networkplumber.org \
--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).