From: Bruce Richardson <bruce.richardson@intel.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: <thomas@monjalon.net>,
Konstantin Ananyev <konstantin.ananyev@huawei.com>,
<dev@dpdk.org>
Subject: Re: [RFC] ethdev: TX mbuf fast release optimization
Date: Thu, 3 Jul 2025 15:14:15 +0100 [thread overview]
Message-ID: <aGaQNxwbTTTF0Al7@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35E9FD87@smartserver.smartshare.dk>
On Thu, Jul 03, 2025 at 03:59:14PM +0200, Morten Brørup wrote:
> For TX mbuf fast release offload, I propose to add the mbuf mempool
> pointer 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.
>
> This modification of the struct rte_eth_txconf, and the requirement
> to set the mempool pointer if the RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE
> flag is set, will be an API+ABI change in 25.11.
> Should it be announced in the 25.07 release notes?
>
> Note: We could phase it in softly by letting the ethdev drivers
> check if the pointer has been set, and fall back to fetching it
> from mbuf[0] if not.
>
> /**
> * A structure used to configure a Tx ring of an Ethernet port.
> */
> struct rte_eth_txconf {
> struct rte_eth_thresh tx_thresh; /**< Tx ring threshold registers. */
> uint16_t tx_rs_thresh; /**< Drives the setting of RS bit on TXDs. */
> uint16_t tx_free_thresh; /**< Start freeing Tx buffers if there are
> less free descriptors than this value. */
>
> uint8_t tx_deferred_start; /**< Do not start queue with rte_eth_dev_start(). */
> /**
> * Per-queue Tx offloads to be set using RTE_ETH_TX_OFFLOAD_* flags.
> * Only offloads set on tx_queue_offload_capa or tx_offload_capa
> * fields on rte_eth_dev_info structure are allowed to be set.
> */
> uint64_t offloads;
>
> + /**
> + * Per-queue mempool to release the mbufs to; required for
> + * RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE offload.
> + */
> + struct rte_mempool *mp;
> +
Is this really best put in the txconf struct? Would it not be better just
stored in the queue structure on free or Tx of the first packet? That would
make it not change the ABI.
/Bruce
next prev parent reply other threads:[~2025-07-03 14:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 13:59 Morten Brørup
2025-07-03 14:14 ` Bruce Richardson [this message]
2025-07-03 15:12 ` Morten Brørup
2025-07-03 15:21 ` Bruce Richardson
2025-07-03 15:29 ` Morten Brørup
2025-07-03 15:35 ` Bruce Richardson
2025-07-03 17:29 ` Morten Brørup
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=aGaQNxwbTTTF0Al7@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=mb@smartsharesystems.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).