From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Olivier Matz" <olivier.matz@6wind.com>,
"Stephen Hemminger" <stephen@networkplumber.org>,
"Van Haaren, Harry" <harry.van.haaren@intel.com>,
"Konstantin Ananyev" <konstantin.ananyev@intel.com>
Cc: <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] mbuf: add bulk free function
Date: Wed, 11 Sep 2019 14:14:12 +0200 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35B42A89@smartserver.smartshare.dk> (raw)
In-Reply-To: <20190911113313.5nrcjvtm5dgi2r76@platinum>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Olivier Matz
>
> Morten, do you have more details about why do you need such a function?
Our application needs it for various purposes, e.g.:
- If rte_eth_tx_burst() returns with not all packets transmitted, our application may decide to drop the unsent packets.
- If there is too much pressure on the system, or an internal queue is full, so it decides to drop packets at some stage. (WAN Optimization appliances tend to buffer large numbers of packets, as opposed to switching/routing appliances.)
Furthermore, try searching DPDK apps/libraries/examples for loops calling rte_pktmbuf_free() with an indexed array... It's copy-paste all over. I would say that this function seems to be missing, and should have been added a long time ago.
>
> Thanks,
> Olivier
Med venlig hilsen / kind regards
- Morten Brørup
prev parent reply other threads:[~2019-09-11 12:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 9:19 Morten Brørup
2019-09-11 11:18 ` Stephen Hemminger
2019-09-11 11:29 ` Van Haaren, Harry
2019-09-11 11:41 ` Ananyev, Konstantin
2019-09-15 9:07 ` Morten Brørup
2019-09-15 9:24 ` Morten Brørup
2019-09-11 11:33 ` Olivier Matz
2019-09-11 11:39 ` Stephen Hemminger
2019-09-11 12:14 ` Morten Brørup [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=98CBD80474FA8B44BF855DF32C47DC35B42A89@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=dev@dpdk.org \
--cc=harry.van.haaren@intel.com \
--cc=konstantin.ananyev@intel.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).