From: Stephen Hemminger <stephen@networkplumber.org>
To: Antonio Di Bacco <a.dibacco.ks@gmail.com>
Cc: users@dpdk.org
Subject: Re: Max size for rte_mempool_create
Date: Wed, 9 Feb 2022 13:44:46 -0800 [thread overview]
Message-ID: <20220209134446.403cf13f@hermes.local> (raw)
In-Reply-To: <CAO8pfFmjrm-qkZJh4GYvNd-6jqoyB-HB1PQCrd1oCu6eh_FSdw@mail.gmail.com>
On Wed, 9 Feb 2022 22:20:34 +0100
Antonio Di Bacco <a.dibacco.ks@gmail.com> wrote:
> I have a system with two numa sockets. Each numa socket has 8GB of RAM.
> I reserve a total of 6 hugepages (1G).
>
> When I try to create a mempool (API rte_mempool_create) of 530432 mbufs
> (each one with 9108 bytes) I get a ENOMEM error.
>
> In theory this mempool should be around 4.8GB and the hugepages are enough
> to hold it.
> Why is this failing ?
This is likely becaus the hugepages have to be contiguous and
the kernel has to that many free pages (especially true with 1G pages).
Therefore it is recommended to
configure and reserve huge pages on kernel command line during boot.
next prev parent reply other threads:[~2022-02-09 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 21:20 Antonio Di Bacco
2022-02-09 21:44 ` Stephen Hemminger [this message]
2022-02-09 21:58 ` Antonio Di Bacco
2022-02-09 22:40 ` Stephen Hemminger
2022-02-10 7:24 ` Gabor LENCSE
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=20220209134446.403cf13f@hermes.local \
--to=stephen@networkplumber.org \
--cc=a.dibacco.ks@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).