From: "Wiles, Keith" <keith.wiles@intel.com>
To: Anupam Kapoor <anupam.kapoor@gmail.com>
Cc: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Freeing up Mbuf
Date: Fri, 23 Dec 2016 16:28:25 +0000 [thread overview]
Message-ID: <E4EA0828-DEE6-4EE1-AB2E-2AEB832E04A0@intel.com> (raw)
In-Reply-To: <CAEXHiZH3eyriAOssH_AgNAUs5z1js-2qBG6HLEQ5W4B2oMMz6w@mail.gmail.com>
> On Dec 22, 2016, at 9:54 PM, Anupam Kapoor <anupam.kapoor@gmail.com> wrote:
>
> On Thu, Dec 22, 2016 at 10:17 PM, Kumaraparameshwaran Rathnavel <
> krath@cloudsimple.com> wrote:
>
>> In FreeBSD the user can actually specify the free routine for the mbuf
>> when the transmit routine is called. Is this implemented in DPDK.
>
>
> currently, afaik, dpdk does not provide this functionality. basically,
> there is no way to poll the tx-ring for consumed buffers. or to put it
> another way, rte_eth_tx_burst doesn't synchronously transmit the packets.
A new patch set is being add to support flushing of the tx done ring. Only a couple to PMDs have support today, but more should be coming or you can add a patch to support your NIC.
http://dpdk.org/ml/archives/dev/2016-November/050444.html
>
> --
> kind regards
> anupam
>
>
> In the beginning was the lambda, and the lambda was with Emacs, and Emacs
> was the lambda.
Regards,
Keith
prev parent reply other threads:[~2016-12-23 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 16:47 Kumaraparameshwaran Rathnavel
2016-12-22 17:00 ` Take Ceara
2016-12-24 4:53 ` Kumaraparameshwaran Rathnavel
2016-12-23 3:54 ` Anupam Kapoor
2016-12-23 16:28 ` Wiles, Keith [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=E4EA0828-DEE6-4EE1-AB2E-2AEB832E04A0@intel.com \
--to=keith.wiles@intel.com \
--cc=anupam.kapoor@gmail.com \
--cc=krath@cloudsimple.com \
--cc=users@dpdk.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).