From: "Schumm, Ken" <ken.schumm@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] When are mbufs released back to the mempool?
Date: Tue, 17 Dec 2013 18:13:35 +0000 [thread overview]
Message-ID: <B35F7300EA51774C974164D11E30E3E42DFA11EB@ORSMSX103.amr.corp.intel.com> (raw)
When running l2fwd the number of available mbufs returned by rte_mempool_count() starts at 7680 on an idle system.
As traffic commences the count declines from 7680 to 5632 (expected).
When traffic stops the count does not climb back to the starting value, indicating that idle mbufs are not returned to the mempool.
For the LCORE cache the doc states
"While this may mean a number of buffers may sit idle on some core's cache, the speed
at which a core can access its own cache for a specific memory pool without locks
provides performance gains"
which makes sense.
Is this also true of ring buffers?
We need to understand when packets are released back to the mempool and with l2fwd it appears that they never are, at least not all of them.
Thanks!
next reply other threads:[~2013-12-17 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 18:13 Schumm, Ken [this message]
2013-12-18 9:02 ` Olivier MATZ
2013-12-19 19:09 ` Schumm, Ken
2013-12-19 19:35 ` Stephen Hemminger
2013-12-19 23:56 ` Schumm, Ken
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=B35F7300EA51774C974164D11E30E3E42DFA11EB@ORSMSX103.amr.corp.intel.com \
--to=ken.schumm@intel.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).