From: Stephen Hemminger <stephen@networkplumber.org>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org
Subject: Re: [PATCH] doc: announce removal of flow director
Date: Thu, 28 May 2026 11:29:18 -0700 [thread overview]
Message-ID: <20260528112918.427a5e45@phoenix.local> (raw)
In-Reply-To: <ED4MTOXhQ4iCVj0Gg4IMwg@monjalon.net>
On Thu, 28 May 2026 20:19:15 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:
> 28/05/2026 19:00, Stephen Hemminger:
> > There are still leftover bits in ethdev related to flow director (fdir).
> > Will be removing these in 26.11 so give final notice.
> >
> > Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> > ---
> > +* ethdev: The legacy filtering data structures in ``rte_eth_ctrl.h``,
> > + including the flow director (FDIR) types (``rte_eth_fdir_*``, ``rte_fdir_*``)
> > + and the ntuple/ethertype/SYN/tunnel/input-set filter types, are superseded
> > + by the ``rte_flow`` API and will be removed in DPDK 26.11. The associated
> > + driver-facing definitions in ``ethdev_driver.h`` (``RTE_ETH_FILTER_FDIR``,
> > + ``struct rte_eth_fdir_conf``, ``enum rte_eth_fdir_pballoc_type``,
> > + ``enum rte_fdir_status_mode``) will be removed at the same time.
>
> The problem is that some drivers rely on these structures for rte_flow.
>
> Note: this file is big, please keep it sorted by moving this
> close to other ethdev and flow deprecations.
There are three cases of drivers using fdir:
- simple ones which are just borrowing things like rte_filter_type
addressing these is trivial; mostly just keep rte_filter_type for now
- Intel ones like i40e and ixgbe which still expose fdir api's.
Can deprecate the PMD API's and move the fdir structures into intel commonc code.
- drivers where fdir was used in variable names but never really used the infrastructure.
Will have proposed patches in a few days.
prev parent reply other threads:[~2026-05-28 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 17:00 [PATCH] doc: announce removal of flow director Stephen Hemminger
2026-05-28 18:19 ` Thomas Monjalon
2026-05-28 18:29 ` Stephen Hemminger [this message]
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=20260528112918.427a5e45@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.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