DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [RFC 6/8] doc: announce legacy flow director deprecation
Date: Thu, 28 May 2026 14:37:18 -0700	[thread overview]
Message-ID: <20260528213816.562910-7-stephen@networkplumber.org> (raw)
In-Reply-To: <20260528213816.562910-1-stephen@networkplumber.org>

Add the formal deprecation notice for the legacy flow director API
and the matching 26.07 release note.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/rel_notes/deprecation.rst   |  7 +++++++
 doc/guides/rel_notes/release_26_07.rst | 14 ++++++++++++++
 2 files changed, 21 insertions(+)

diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index d152e76fdc..5e2949d153 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -131,6 +131,13 @@ Deprecation Notices
   The legacy actions should be removed
   once ``MODIFY_FIELD`` alternative is implemented in drivers.
 
+* ethdev: Legacy flow director API will be removed in DPDK 26.11.
+  This affects: flow director data structures in ``rte_eth_ctrl.h``
+  (``rte_eth_fdir_*`` and ``rte_fdir_*`` types and the associated
+  ``RTE_ETH_FDIR_*`` / ``RTE_FDIR_*`` macros) and the driver-facing
+  definitions in ``ethdev_driver.h`` (``struct rte_eth_fdir_conf``,
+  ``enum rte_eth_fdir_pballoc_type``, ``enum rte_fdir_status_mode``).
+
 * cryptodev: Support for OpenSSL versions earlier than 3.0 is deprecated
   and will be removed. OpenSSL 1.1.1 reached end-of-life in September 2023.
   The minimum supported OpenSSL version will be 3.0,
diff --git a/doc/guides/rel_notes/release_26_07.rst b/doc/guides/rel_notes/release_26_07.rst
index 8b4f8401e2..06689cdcca 100644
--- a/doc/guides/rel_notes/release_26_07.rst
+++ b/doc/guides/rel_notes/release_26_07.rst
@@ -100,6 +100,18 @@ Removed Items
    Also, make sure to start the actual text at the margin.
    =======================================================
 
+* Removed legacy flow director artifacts that depended on deprecated API.
+  Users should use ``rte_flow`` API and testpmd ``flow``
+  command instead.
+
+  * app/testpmd: ``show port fdir``, ``clear port fdir``,
+    ``flow_director_filter``, ``port config ... pctype mapping ...``,
+    and ``port config ... hash_inset|fdir_inset|fdir_flx_inset ...``.
+
+  * net/i40e, net/ixgbe: the experimental
+    ``rte_pmd_{i40e,ixgbe}_get_fdir_info()`` and
+    ``rte_pmd_{i40e,ixgbe}_get_fdir_stats()`` functions.
+
 
 API Changes
 -----------
@@ -116,6 +128,8 @@ API Changes
    Also, make sure to start the actual text at the margin.
    =======================================================
 
+* Deprecated the legacy flow director API; removal scheduled for
+  DPDK 26.11. Use the ``rte_flow`` API instead.
 
 ABI Changes
 -----------
-- 
2.53.0


  parent reply	other threads:[~2026-05-28 21:39 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28 21:37 [RFC 0/8] retire legacy flow director API Stephen Hemminger
2026-05-28 21:37 ` [RFC 1/8] app/testpmd: remove support for flow director Stephen Hemminger
2026-05-28 21:37 ` [RFC 2/8] net/i40e: remove testpmd flow filter commands Stephen Hemminger
2026-05-28 21:37 ` [RFC 3/8] net/i40e: deprecate legacy flow filter API Stephen Hemminger
2026-05-28 21:37 ` [RFC 4/8] net/i40e: remove experimental FDIR API Stephen Hemminger
2026-05-28 21:37 ` [RFC 5/8] net/ixgbe: " Stephen Hemminger
2026-05-28 21:37 ` Stephen Hemminger [this message]
2026-05-28 21:37 ` [RFC 7/8] net/ixgbe: privatize legacy flow director types Stephen Hemminger
2026-05-28 21:37 ` [RFC 8/8] net/txgbe: " Stephen Hemminger
2026-05-29  7:29   ` Jiawen Wu

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=20260528213816.562910-7-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --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