From: Stephen Hemminger <stephen@networkplumber.org>
To: amit sehas <cun23@yahoo.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: rte_pktmbuf_alloc() out of rte_mbufs
Date: Fri, 22 Nov 2024 08:45:57 -0800 [thread overview]
Message-ID: <20241122084557.726e38e7@hermes.local> (raw)
In-Reply-To: <67781150.1429748.1732243135675@mail.yahoo.com>
On Fri, 22 Nov 2024 02:38:55 +0000 (UTC)
amit sehas <cun23@yahoo.com> wrote:
> I am frequently running into out of mbufs when allocating packets. When this happens is there a way to dump counts of which buffers are where so we know what is going on?
>
> I know that each rte_mbuf pool also has per cpu core cache to speed up alloc/free, and some of the buffers will end up there and if one were to never utilize a particular core for a particular mpool perhaps those mbufs are lost ... that is my rough guess ...
>
> How do you debug out of mbufs issue?
>
> regards
The function rte_mempool_dump() will tell you some information about the status of a particular mempool.
If you enable mempool statistics you can get more info.
The best way to size a memory pool is to account for all the possible places mbuf's can be waiting.
Something like:
Num Port * Num RxQ * Num RxD + Num Port * Num TxQ * Num TxD + Num Lcores * Burst Size + Num Lcores * Cache size
Often running out of mbufs is because of failure to free an recveived mbuf, or a buggy driver.
prev parent reply other threads:[~2024-11-22 16:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <67781150.1429748.1732243135675.ref@mail.yahoo.com>
2024-11-22 2:38 ` amit sehas
2024-11-22 16:45 ` Stephen Hemminger [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=20241122084557.726e38e7@hermes.local \
--to=stephen@networkplumber.org \
--cc=cun23@yahoo.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).