DPDK patches and discussions
 help / color / mirror / Atom feed
From: Vithal S Mohare <vmohare@arubanetworks.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Callbacks after buffer  (mbuf) sent out
Date: Fri, 16 Jan 2015 07:17:11 +0000	[thread overview]
Message-ID: <98DB008FA2AC6644B40AD8C766FAB271014BDE87EE@BOREAL.arubanetworks.com> (raw)
In-Reply-To: <98DB008FA2AC6644B40AD8C766FAB271014BDE7723@BOREAL.arubanetworks.com>

To elaborate more...
Assuming an example of vmxnet3 driver, at present, when rte_eth_tx_burst() is called to send mbufs, vmxnet3 driver calls vmxnet3_tq_tx_complete() to free up  completed buffers.  Instead, wondering, if vmxnet3 (or corresponding driver) can trigger application callback for the buffer (mbuf) which gets transmitted out of n/w interface.  Application callback can decide now decide whether to reuse the mbuf and continue multicasting on other tunnels.  

Thanks,
-Vithal

-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Vithal S Mohare
Sent: Tuesday, January 13, 2015 9:21 AM
To: dev@dpdk.org
Subject: [dpdk-dev] Callbacks after buffer (mbuf) sent out

Hi,

I am looking for application callbacks after mbufs are sent (tx) out successfully.   One of the use cases is for async multicast (over different gre tunnels etc).   Using direct/indirect buffers along with ref-count itself is not enough, as actual 'pkt-data' itself changes while flooding on list of tunnels.

Thanks,
-Vithal

      reply	other threads:[~2015-01-16  7:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-13  3:51 Vithal S Mohare
2015-01-16  7:17 ` Vithal S Mohare [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=98DB008FA2AC6644B40AD8C766FAB271014BDE87EE@BOREAL.arubanetworks.com \
    --to=vmohare@arubanetworks.com \
    --cc=dev@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).