From: Olivier Matz <olivier.matz@6wind.com>
To: "Morten Brørup" <mb@smartsharesystems.com>
Cc: dev@dpdk.org
Subject: Re: RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE requirements
Date: Fri, 22 Jul 2022 17:24:11 +0200 [thread overview]
Message-ID: <YtrBGxVnfJWdU+UE@platinum> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35D871C5@smartserver.smartshare.dk>
Hi Morten,
Yes, you are right. These 2 conditions are also needed if one wants to use
rte_mbuf_raw_free() or rte_mempool_put*() functions to free the mbufs.
Olivier
On Thu, Jul 14, 2022 at 12:46:24PM +0200, Morten Brørup wrote:
> Looking at rte_pktmbuf_prefree_seg() [1], the list of described requirements for RTE_ETH_TX_OFFLOAD_MBUF_FAST_FREE [2] seems incomplete. The following two requirements are missing:
> - The mbufs must be direct.
> - The mbufs must be non-segmented.
>
> [1] https://elixir.bootlin.com/dpdk/latest/source/lib/mbuf/rte_mbuf.h#L1308
> [2] https://elixir.bootlin.com/dpdk/latest/source/lib/ethdev/rte_ethdev.h#L1701
>
>
> Med venlig hilsen / Kind regards,
> -Morten Brørup
>
prev parent reply other threads:[~2022-07-22 15:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 10:46 Morten Brørup
2022-07-22 15:24 ` Olivier Matz [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=YtrBGxVnfJWdU+UE@platinum \
--to=olivier.matz@6wind.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.com \
/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).