From: "Morten Brørup" <mb@smartsharesystems.com>
To: dev@dpdk.org
Cc: olivier.matz@6wind.com, stephen@networkplumber.org,
harry.van.haaren@intel.com, konstantin.ananyev@intel.com,
mattias.ronnblom@ericsson.com, bruce.richardson@intel.com,
arybchenko@solarflare.com,
"Morten Brørup" <mb@smartsharesystems.com>
Subject: [dpdk-dev] [PATCH v9 0/2] mbuf: add bulk free function
Date: Wed, 23 Oct 2019 10:11:09 +0000 [thread overview]
Message-ID: <20191023101111.81742-1-mb@smartsharesystems.com> (raw)
Add function for freeing a bulk of mbufs.
Add unit test for functions for allocating and freeing a bulk of mbufs.
Signed-off-by: Morten Brørup <mb@smartsharesystems.com>
Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Reviewed-by: Andrew Rybchenko <arybchenko@solarflare.com>
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Olivier Matz <olivier.matz@6wind.com>
---
v9:
* Fix a typo in a description.
* In the unit test, make chain length a #define and add a few
RTE_BUILD_BUG_ON().
* The unit test prints when allocating the mbuf pools for the bulk tests.
Also print when freeing them.
v8:
* Add unit test, covering both bulk alloc and bulk free.
v7:
* Squash multiple modifications into one.
v6:
* Remove __rte_always_inline from static function.
The compiler will inline anyway.
v5:
* Rename variables from "free" to "pending" for improved readability.
* Add prefix __ to rte_pktmbuf_free_seg_via_array().
* Add array size parameter to __rte_pktmbuf_free_seg_via_array().
The compiler will optimize the parameter away anyway.
* Add description to __rte_pktmbuf_free_seg_via_array().
* Minor description updates.
v4:
* Mark as experimental by adding __rte_experimental.
* Add function to experimental section of map file.
* Fix source code formatting regarding pointer to pointer.
* Squash multiple modifications into one.
v3:
* Bugfix: Handle pakets with multiple segments.
* Add inline helper function, mainly for readability.
* Fix source code formatting regarding indentation.
v2:
* Function is not inline.
* Optimize to free multible mbufs belonging to the same mempool in
bulk. Inspired by ixgbe_tx_free_bufs(), but allowing NULL pointers
in the array, just like rte_pktmbuf_free() can take a NULL pointer.
* Use unsigned int instead of unsigned. Passes checkpatch, but
mismatches the original coding style of the modified files.
* Fix a typo in the description headline: mempools is plural.
Morten Brørup (2):
mbuf: add bulk free function
mbuf: add unit test for bulk alloc/free functions
app/test/test_mbuf.c | 179 +++++++++++++++++++++++++++
lib/librte_mbuf/rte_mbuf.c | 66 ++++++++++
lib/librte_mbuf/rte_mbuf.h | 15 +++
lib/librte_mbuf/rte_mbuf_version.map | 1 +
4 files changed, 261 insertions(+)
--
2.17.1
next reply other threads:[~2019-10-23 10:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 10:11 Morten Brørup [this message]
2019-10-23 10:11 ` [dpdk-dev] [PATCH v9 1/2] " Morten Brørup
2019-10-23 10:11 ` [dpdk-dev] [PATCH v9 2/2] mbuf: add unit test for bulk alloc/free functions Morten Brørup
2019-10-24 0:48 ` [dpdk-dev] [PATCH v9 0/2] mbuf: add bulk free function Thomas Monjalon
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=20191023101111.81742-1-mb@smartsharesystems.com \
--to=mb@smartsharesystems.com \
--cc=arybchenko@solarflare.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=mattias.ronnblom@ericsson.com \
--cc=olivier.matz@6wind.com \
--cc=stephen@networkplumber.org \
/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).