From: Antonio Di Bacco <a.dibacco.ks@gmail.com>
To: stephen@networkplumber.org
Cc: users@dpdk.org
Subject: Re: Max size for rte_mempool_create
Date: Wed, 9 Feb 2022 22:58:43 +0100 [thread overview]
Message-ID: <CAO8pfFnS0sOA4cmQ-CR1Gpc+QM3Fuh6L0ZEMm+d2RZ4BEd3SgA@mail.gmail.com> (raw)
In-Reply-To: <20220209134446.403cf13f@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
Thanks! I already reserve huge pages from kernel command line . I reserve 6
1G hugepages. Is there any other reason for the ENOMEM?
On Wed, 9 Feb 2022 at 22:44, Stephen Hemminger <stephen@networkplumber.org>
wrote:
> 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.
>
[-- Attachment #2: Type: text/html, Size: 1419 bytes --]
next prev parent reply other threads:[~2022-02-09 21:58 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
2022-02-09 21:58 ` Antonio Di Bacco [this message]
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=CAO8pfFnS0sOA4cmQ-CR1Gpc+QM3Fuh6L0ZEMm+d2RZ4BEd3SgA@mail.gmail.com \
--to=a.dibacco.ks@gmail.com \
--cc=stephen@networkplumber.org \
--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).