15/07/2025 17:12, Konstantin Ananyev: > > > For TX mbuf fast release offload, the mbuf mempool pointer will be added > > to the ethdev tx queue configuration structure, so the ethdev TX burst > > operation doesn't need to fetch it from the first mbuf of each burst being > > fast free'd to the mempool. > > > > Signed-off-by: Morten Brørup <m...@smartsharesystems.com> > > --- > > doc/guides/rel_notes/deprecation.rst | 6 ++++++ > > 1 file changed, 6 insertions(+) > > > > diff --git a/doc/guides/rel_notes/deprecation.rst > > b/doc/guides/rel_notes/deprecation.rst > > index e2d4125308..a7b4505a24 100644 > > --- a/doc/guides/rel_notes/deprecation.rst > > +++ b/doc/guides/rel_notes/deprecation.rst > > @@ -152,3 +152,9 @@ Deprecation Notices > > * bus/vmbus: Starting DPDK 25.11, all the vmbus API defined in > > ``drivers/bus/vmbus/rte_bus_vmbus.h`` will become internal to DPDK. > > Those API functions are used internally by DPDK core and netvsc PMD. > > + > > +* ethdev: Configuring a transmit queue for fast mbuf release will > > + require specifying which mempool to free the mbufs to. > > + For this, a new field ``struct rte_mempool *mp_fast_free`` will be > > + added to ``struct rte_eth_txconf``, and must be set when the > > + ``RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE`` offload flag is set. > > -- > > Acked-by: Konstantin Ananyev <konstantin.anan...@huawei.com>
Looks like this new requirement is not encouraged a lot. Per our policy, it will miss the release 25.07.
