From: Andriy Berestovskyy <aber@semihalf.com>
To: "Javier Coleto Fernández" <javicoleto44@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] mbuf free cnt not decreasing
Date: Mon, 18 Apr 2016 11:21:44 +0200 [thread overview]
Message-ID: <CAOysbxqQ78cavhAJV8WJXViN2YKO5-KmxJHbT0bFugOyDMG-rA@mail.gmail.com> (raw)
In-Reply-To: <CABbgvkvYVic4xHxPnsmep-Gch14PBBaAcb8rdW2ZN1sf2b6E6g@mail.gmail.com>
Hi Javier,
Please make sure you check the return value of rte_kni_tx_burst() and
rte_eth_tx_burst() and free the unsent mbufs. Might be something
else...
Overall the technique should be the same as with memory leaks: debug
logs and patience ;)
Regards,
Andriy
On Mon, Apr 18, 2016 at 10:41 AM, Javier Coleto Fernández
<javicoleto44@gmail.com> 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.
>
> Regards,
> Javier
--
Andriy Berestovskyy
next prev parent reply other threads:[~2016-04-18 9:22 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 [this message]
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
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=CAOysbxqQ78cavhAJV8WJXViN2YKO5-KmxJHbT0bFugOyDMG-rA@mail.gmail.com \
--to=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).