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: Fri, 15 Apr 2016 15:01:23 +0200 [thread overview]
Message-ID: <CAOysbxoXvywFhhk+yAofSZ6_HEan8Yoi90NumQsvP_vZ8=UySg@mail.gmail.com> (raw)
In-Reply-To: <CABbgvkurz25E9VZZCi=FJaPDbVQF2ky-vu1w-+bQTEZRauPP_Q@mail.gmail.com>
Hi Javier,
Please see below.
On Fri, Apr 15, 2016 at 10:34 AM, Javier Coleto Fernández
<javicoleto44@gmail.com> wrote:
> The problem I'm facing is my mbuf free count (as given by
> rte_mempool_free_count()) keeps increasing and tops at ~8130. Being 8192
> the size of the mempool, that stops the packet processing and my
> application stops forwarding.
Try rte_ring_count(mempool->ring) instead of rte_mempool_free_count().
The latter adds cached mbufs, hence might be the difference 8192 vs
8130.
> Any clues about what I could do to liberate the free mbufs back to the
> mempool?
Try to increase the number of mbufs in the mempool. There might be two cases:
1. For whatever mempool size you always lack mbufs -> it is an mbuf
leak, so you have to find and fix it.
2. Number of free mbufs stabilizes at some point -> you could either
increase the mempool size to accommodate that usage or reduce the
caches/descriptors/thresholds.
Andriy
next prev parent reply other threads:[~2016-04-15 13:01 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 [this message]
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
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='CAOysbxoXvywFhhk+yAofSZ6_HEan8Yoi90NumQsvP_vZ8=UySg@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).