From: Thomas Monjalon <thomas@monjalon.net>
To: Mohammad Masumi <mmasumi@gmail.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: "users@dpdk.org" <users@dpdk.org>,
"dmitry.kozliuk@gmail.com" <dmitry.kozliuk@gmail.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: Re: [dpdk-users] Memory allocation limits
Date: Wed, 29 Sep 2021 13:12:03 +0200 [thread overview]
Message-ID: <1758092.NzVlmGAOTI@thomas> (raw)
In-Reply-To: <PH0PR11MB509303BFA63B5C9EF0888A8BF7A99@PH0PR11MB5093.namprd11.prod.outlook.com>
29/09/2021 12:14, Burakov, Anatoly:
> From: Thomas Monjalon <thomas@monjalon.net>
> > 26/09/2021 17:52, Mohammad Masumi:
> > > Hi
> > >
> > > I have HP server with 768GB memory 384GB in each Numa but I can't
> > > allocate more than 64GB by rte_malloc by changing some parameters in
> > > rte_config.h it increased to 128GB How to increase heap size?
> >
> > adding people Cc to help
> >
>
> Hi,
>
> This is intentional. In order to increase the amount of contiguous allocation possible to perform in DPDK, you need to adjust the following values in rte_config.h:
>
> #define RTE_MAX_MEMSEG_PER_LIST 8192
> #define RTE_MAX_MEM_MB_PER_LIST 32768
> #define RTE_MAX_MEMSEG_PER_TYPE 32768
> #define RTE_MAX_MEM_MB_PER_TYPE 65536
>
> I do not recommend arbitrarily changing them as this is untested, but increasing them proportionally (e.g. multiply all of them by 2 or 4) should not break anything.
It looks to be something to add in docs, right?
next prev parent reply other threads:[~2021-09-29 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 15:52 Mohammad Masumi
2021-09-29 9:58 ` Thomas Monjalon
2021-09-29 10:14 ` Burakov, Anatoly
2021-09-29 11:12 ` Thomas Monjalon [this message]
2021-09-29 12:43 ` Burakov, Anatoly
2021-09-29 12:55 ` Thomas Monjalon
2022-04-01 20:43 Dave Sclarsky
2022-04-01 21:42 Dave Sclarsky
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=1758092.NzVlmGAOTI@thomas \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dmitry.kozliuk@gmail.com \
--cc=mmasumi@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).