DPDK patches and discussions
 help / color / mirror / Atom feed
From: Paras Jha <dreadiscool@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] rte_eth_tx_burst improperly freeing mbufs from KNI mbuf pool
Date: Wed, 10 Apr 2019 09:10:33 -0400	[thread overview]
Message-ID: <CAMs8r4M25oYOs=G0+jrAz+=QFj2CFisXTZJ=Pp4FhAZpUDj=2Q@mail.gmail.com> (raw)
Message-ID: <20190410131033.GHPeh6-NwMUR6wIiq0SQ9y6z-PYOo0YO895ym0eR6Co@z> (raw)

Hi all,

I've been chasing down a strange issue related to rte_kni_tx_burst.

My application calls rte_kni_rx_burst, which allocates from a discrete mbuf
pool using kni_allocate_mbufs. That traffic is immediately sent to
rte_eth_tx_burst which does not seem to be freeing mbufs even upon
succesful completion.

My application follows the standard model of freeing mbufs only if the
number of tx mbufs is less than the rx mbufs - however, after sending as
many mbufs as there are in the pool, I get KNI: Out of memory soon after
when calling rte_kni_rx_burst

My concern is that if I free all mbufs allocated by the KNI during
rte_kni_rx_burst the application seems to work as intended without memory
leaks, even though this goes against how the actual PMDs work. Is this a
bug, or intended behavior? The documented examples on the DPDK website seem
to only free mbufs if it fails to send, even with the KNI example.

B/R

             reply	other threads:[~2019-04-10 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-10 13:10 Paras Jha [this message]
2019-04-10 13:10 ` Paras Jha
2019-04-30 14:59 ` Ferruh Yigit
2019-04-30 14:59   ` Ferruh Yigit
2019-04-30 15:37   ` Paras Jha
2019-04-30 15:37     ` Paras Jha
2019-04-30 15:39     ` Paras Jha
2019-04-30 15:39       ` Paras Jha

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='CAMs8r4M25oYOs=G0+jrAz+=QFj2CFisXTZJ=Pp4FhAZpUDj=2Q@mail.gmail.com' \
    --to=dreadiscool@gmail.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).