From: "Morten Brørup" <mb@smartsharesystems.com>
To: olivier.matz@6wind.com
Cc: stephen@networkplumber.org, harry.van.haaren@intel.com,
konstantin.ananyev@intel.com, mattias.ronnblom@ericsson.com,
bruce.richardson@intel.com, arybchenko@solarflare.com,
dev@dpdk.org, "Morten Brørup" <mb@smartsharesystems.com>
Subject: [dpdk-dev] [PATCH v4 0/1] mbuf: add bulk free function
Date: Mon, 7 Oct 2019 10:14:26 +0000 [thread overview]
Message-ID: <20191007101427.16191-1-mb@smartsharesystems.com> (raw)
Add function for freeing a bulk of mbufs.
v4:
* Marked as experimental by adding __rte_experimental.
* Add function to experimental section of map file.
* Fix source code formatting regarding pointer to pointer.
* Squashed multiple modifications into one.
v3:
* Bugfix: Handle pakets with multiple segments.
* Added inline helper function, mainly for readability.
* Fix source code formatting regarding indentation.
v2:
* Function is not inline.
* Optimized 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.
* Fixed a typo in the description headline: mempools is plural.
Morten Brørup (1):
mbuf: add bulk free function
lib/librte_mbuf/rte_mbuf.c | 50 ++++++++++++++++++++++++++++
lib/librte_mbuf/rte_mbuf.h | 12 +++++++
lib/librte_mbuf/rte_mbuf_version.map | 1 +
3 files changed, 63 insertions(+)
--
2.17.1
next reply other threads:[~2019-10-07 10:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 10:14 Morten Brørup [this message]
2019-10-07 10:14 ` [dpdk-dev] [PATCH v4 1/1] " Morten Brørup
2019-10-08 17:25 ` Andrew Rybchenko
2019-10-08 20:12 ` Morten Brørup
2019-10-09 6:46 ` Andrew Rybchenko
2019-10-09 9:32 ` Ananyev, Konstantin
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=20191007101427.16191-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).