DPDK usage discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Javier Coleto Fernández" <javicoleto44@gmail.com>,
	"Andriy Berestovskyy" <aber@semihalf.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] mbuf free cnt not decreasing
Date: Mon, 18 Apr 2016 15:53:38 +0100	[thread overview]
Message-ID: <5714F4F2.3040703@intel.com> (raw)
In-Reply-To: <CABbgvkvYVic4xHxPnsmep-Gch14PBBaAcb8rdW2ZN1sf2b6E6g@mail.gmail.com>

On 4/18/2016 9:41 AM, Javier Coleto Fernández wrote:
> Hi Andriy,
> 
> Thank you for your answer.
> I've tried what you said and determined it's an mbuf leak, because the
> number of free mbufs doesn't stabilize, even when I increase the number of
> mbufs in the mempool.
> Is there any way to easily debug this mbuf leak? I didn't make the full
> code, so I don't really know where to start looking for leaks.
> 

Can you please check free_q?
kni_fifo_free_count(kni->free_q)

If you call rte_kni_tx_burst() for more than 32 packets at a time, mbufs
may stuck in free_q.

Regards,
ferruh

      parent reply	other threads:[~2016-04-18 14:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-15  8:34 Javier Coleto Fernández
2016-04-15 13:01 ` Andriy Berestovskyy
2016-04-18  8:41   ` Javier Coleto Fernández
2016-04-18  9:21     ` Andriy Berestovskyy
2016-04-18 14:37       ` Wiles, Keith
2016-04-18 15:34         ` Javier Coleto Fernández
2016-04-18 15:57           ` Andriy Berestovskyy
2016-04-18 16:01             ` Javier Coleto Fernández
2016-04-18 16:13               ` Andriy Berestovskyy
2016-04-18 16:29                 ` Wiles, Keith
2016-04-18 16:41                   ` Javier Coleto Fernández
2016-04-18 16:44                     ` Wiles, Keith
2016-04-19 11:30                       ` Javier Coleto Fernández
2016-04-18 14:53     ` Ferruh Yigit [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=5714F4F2.3040703@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=aber@semihalf.com \
    --cc=javicoleto44@gmail.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).