DPDK usage discussions
 help / color / mirror / Atom feed
From: Kumaraparameshwaran Rathnavel <krath@cloudsimple.com>
To: users@dpdk.org
Subject: [dpdk-users] Freeing up Mbuf
Date: Thu, 22 Dec 2016 22:17:18 +0530	[thread overview]
Message-ID: <35D0462D-761F-4C7A-A0F4-FD72EBDFA8EB@cloudsimple.com> (raw)

Hi All,

The mbuf implementation is similar to the Network Driver of the FreeBSD Network Driver. In DPDK userspace driver it is the responsibility of the rte_eth_dev implementation to free the memory buffer associated with a Queue when descriptors reach below a threshold. In FreeBSD the user can actually specify the free routine for the mbuf when the transmit routine is called. Is this implemented in DPDK. I basically will give the data buffer of the application layer that will be chained with the Transport Layer Headers and I do not want to free up the routines always. Is this possible?

Thanking You,
Param.

             reply	other threads:[~2016-12-22 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 16:47 Kumaraparameshwaran Rathnavel [this message]
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

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=35D0462D-761F-4C7A-A0F4-FD72EBDFA8EB@cloudsimple.com \
    --to=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).