From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: adrien.mazarguil@6wind.com, shahafs@mellanox.com,
david.marchand@redhat.com, jerinj@marvell.com,
arybchenko@solarflare.com, ferruh.yigit@intel.com,
bruce.richardson@intel.com, hemant.agrawal@nxp.com,
stephen@networkplumber.org, ajit.khaparde@broadcom.com,
johndale@cisco.com, xavier.huwei@huawei.com,
xuanziyang2@huawei.com, wei.zhao1@intel.com, rmody@marvell.com
Subject: [dpdk-dev] [PATCH] doc: announce removal of ethdev flow director API
Date: Mon, 3 Aug 2020 19:49:09 +0200 [thread overview]
Message-ID: <20200803174909.3290046-1-thomas@monjalon.net> (raw)
The flow director config, part of the legacy filtering API,
was marked as deprecated last year.
A separate notice is added to make clear that these specific structs
will be removed as well in DPDK 20.11, as the rest of the legacy
filtering API.
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/rel_notes/deprecation.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ea4cfa7a48..24474c563f 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -84,6 +84,10 @@ Deprecation Notices
Target release for removal of the legacy API will be defined once most
PMDs have switched to rte_flow.
+* ethdev: The flow director API, including ``rte_eth_conf.fdir_conf`` field,
+ and the related structures (``rte_fdir_*`` and ``rte_eth_fdir_*``),
+ will be removed in DPDK 20.11.
+
* ethdev: Update API functions returning ``void`` to return ``int`` with
negative errno values to indicate various error conditions (e.g.
invalid port ID, unsupported operation, failed operation):
--
2.27.0
next reply other threads:[~2020-08-03 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-03 17:49 Thomas Monjalon [this message]
2020-08-03 17:57 ` Ajit Khaparde
2020-08-04 3:51 ` Jerin Jacob
2020-08-05 13:46 ` Andrew Rybchenko
2020-08-06 0:30 ` Thomas Monjalon
2020-08-04 7:36 ` David Marchand
2020-08-04 7:49 ` Hemant Agrawal
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=20200803174909.3290046-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=ajit.khaparde@broadcom.com \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=johndale@cisco.com \
--cc=rmody@marvell.com \
--cc=shahafs@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=wei.zhao1@intel.com \
--cc=xavier.huwei@huawei.com \
--cc=xuanziyang2@huawei.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).