From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Thomas Monjalon <thomas@monjalon.net>,
Ferruh Yigit <ferruh.yigit@xilinx.com>
Cc: dev@dpdk.org, Qiming Yang <qiming.yang@intel.com>,
Wenjun Wu <wenjun1.wu@intel.com>,
Yuying Zhang <Yuying.Zhang@intel.com>,
Beilei Xing <beilei.xing@intel.com>,
Rasesh Mody <rmody@marvell.com>,
Devendra Singh Rawat <dsinghrawat@marvell.com>,
Jiawen Wu <jiawenwu@trustnetic.com>,
Jian Wang <jianwang@trustnetic.com>
Subject: [PATCH 0/3] ethdev: remove deprecated Flow Director configuration
Date: Wed, 3 Aug 2022 14:13:55 +0300 [thread overview]
Message-ID: <20220803111358.375544-1-andrew.rybchenko@oktetlabs.ru> (raw)
Flow Director configuration fdir_conf was deprecated long time ago and
was planned to be removed in 20.11.
i40e, ixgbe, qede and txgbe driver maintainers are encouraged to review
correspodning patches very carefully.
Internal copy of the Flow Director configuration in ixgbe and txgbe
drivers is not actually initialized. Should I use configuration from
testpmd as the default one?
Andrew Rybchenko (3):
net/ixgbe: add helper to get Flow Director configuration
net/txgbe: add helper to get Flow Director configuration
ethdev: remove deprecated Flow Director configuration
app/test-pmd/cmdline.c | 343 --------------------
app/test-pmd/config.c | 100 ------
app/test-pmd/parameters.c | 76 -----
app/test-pmd/testpmd.c | 24 --
app/test-pmd/testpmd.h | 6 -
doc/guides/nics/fm10k.rst | 2 -
doc/guides/nics/ixgbe.rst | 1 -
doc/guides/rel_notes/deprecation.rst | 4 -
doc/guides/rel_notes/release_22_11.rst | 4 +
doc/guides/testpmd_app_ug/run_app.rst | 27 --
doc/guides/testpmd_app_ug/testpmd_funcs.rst | 38 ---
drivers/net/cnxk/cnxk_ethdev.c | 5 -
drivers/net/fm10k/fm10k_rxtx_vec.c | 5 -
drivers/net/hns3/hns3_rxtx_vec.c | 4 -
drivers/net/i40e/i40e_ethdev.c | 31 --
drivers/net/i40e/i40e_fdir.c | 304 +----------------
drivers/net/i40e/i40e_rxtx_vec_common.h | 5 -
drivers/net/ixgbe/ixgbe_ethdev.c | 2 +-
drivers/net/ixgbe/ixgbe_ethdev.h | 4 +
drivers/net/ixgbe/ixgbe_fdir.c | 32 +-
drivers/net/ixgbe/ixgbe_flow.c | 13 +-
drivers/net/ixgbe/ixgbe_rxtx_vec_common.h | 2 +-
drivers/net/octeontx/octeontx_ethdev.c | 5 -
drivers/net/qede/qede_filter.c | 29 +-
drivers/net/sfc/sfc.c | 5 -
drivers/net/sfc/sfc_repr.c | 5 -
drivers/net/thunderx/nicvf_ethdev.c | 5 -
drivers/net/txgbe/txgbe_ethdev.c | 2 +-
drivers/net/txgbe/txgbe_ethdev.h | 3 +
drivers/net/txgbe/txgbe_fdir.c | 24 +-
drivers/net/txgbe/txgbe_flow.c | 13 +-
lib/ethdev/ethdev_driver.h | 36 ++
lib/ethdev/rte_ethdev.h | 43 ---
33 files changed, 100 insertions(+), 1102 deletions(-)
--
2.30.2
next reply other threads:[~2022-08-03 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 11:13 Andrew Rybchenko [this message]
2022-08-03 11:13 ` [PATCH 1/3] net/ixgbe: add helper to get " Andrew Rybchenko
2022-08-03 11:13 ` [PATCH 2/3] net/txgbe: " Andrew Rybchenko
2022-08-03 11:13 ` [PATCH 3/3] ethdev: remove deprecated " Andrew Rybchenko
2022-08-04 11:07 ` Dongdong Liu
2022-08-24 9:42 ` [PATCH 0/3] " Ferruh Yigit
2022-08-31 13:27 ` Ferruh Yigit
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=20220803111358.375544-1-andrew.rybchenko@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=Yuying.Zhang@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=dsinghrawat@marvell.com \
--cc=ferruh.yigit@xilinx.com \
--cc=jianwang@trustnetic.com \
--cc=jiawenwu@trustnetic.com \
--cc=qiming.yang@intel.com \
--cc=rmody@marvell.com \
--cc=thomas@monjalon.net \
--cc=wenjun1.wu@intel.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).