From: "Morten Brørup" <mb@smartsharesystems.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>
Subject: [PATCH] doc: announce mbuf fast free configuration requirements
Date: Sun, 13 Jul 2025 14:21:27 +0000 [thread overview]
Message-ID: <20250713142127.349940-1-mb@smartsharesystems.com> (raw)
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 <mb@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.
--
2.43.0
reply other threads:[~2025-07-13 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250713142127.349940-1-mb@smartsharesystems.com \
--to=mb@smartsharesystems.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--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;
as well as URLs for NNTP newsgroup(s).