From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Kamaraj P <pkamaraj@gmail.com>, dev@dpdk.org
Cc: Nageswara Rao Penumarthy <npenumar@cisco.com>,
"Kamaraj P (kamp)" <kamp@cisco.com>
Subject: Re: [dpdk-dev] CONFIG_RTE_MAX_MEM_MB fails in DPDK18.05
Date: Tue, 10 Dec 2019 10:23:06 +0000 [thread overview]
Message-ID: <5192f94a-e50a-7e61-2e33-a218a4b6b5b4@intel.com> (raw)
In-Reply-To: <CAG8PAapbn2WgDASX2gmkWcnCSycetaOaN85Qt4qwYtuJv9_W-Q@mail.gmail.com>
On 07-Dec-19 5:01 PM, Kamaraj P wrote:
> Hello All,
>
> Currently, we are facing an issue with memory allocation failure
> in memseg_primary_init().
> When we configure the CONFIG_RTE_MAX_MEM_MB to 512MB and correspondingly
> configured the number of huge pages for our platform. But the virtual
> memory allocation is failing.
>
> It appears that its trying to allocate CONFIG_RTE_MAX_MEMSEG_PER_LIST *
> Huge page size (i.e. 8192 * 2MB = 0x400000000) and virtual memory
> allocation is failing.
>
> Also tried changing the CONFIG_RTE_MAX_MEMSEG_PER_LIST to 64 with which
> virtual memory allocation is passing for the 128MB (64 * 2MB). But looks
> like 128MB memory is not enough and it is causing the PCIe enumeration
> failure.
> Not able allocate virtual memory beyond 128MB by increasing the
> CONFIG_RTE_MAX_MEMSEG_PER_LIST beyond 64.
>
> Is there are any settings(argument) which we need to pass as part of
> rte_eal_init()
> to get success in the virtual memory allocation?
> Please advise.
>
> Thanks,
> Kamaraj
>
I don't think there are, as the allocator wasn't designed with such
memory constrained use cases in mind. You may want to try --legacy-mem
option.
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-12-10 10:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 17:01 Kamaraj P
2019-12-10 10:23 ` Burakov, Anatoly [this message]
2020-02-17 9:57 ` Kamaraj P
2020-02-19 10:23 ` Burakov, Anatoly
2020-02-19 10:56 ` Kevin Traynor
2020-02-19 11:16 ` Kamaraj P
2020-02-19 14:23 ` Burakov, Anatoly
2020-02-19 15:02 ` Kamaraj P
2020-02-19 15:28 ` Burakov, Anatoly
2020-02-19 15:42 ` Kamaraj P
2020-02-19 16:00 ` Burakov, Anatoly
2020-02-19 16:20 ` Kamaraj P
2020-02-20 10:02 ` Burakov, Anatoly
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=5192f94a-e50a-7e61-2e33-a218a4b6b5b4@intel.com \
--to=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=kamp@cisco.com \
--cc=npenumar@cisco.com \
--cc=pkamaraj@gmail.com \
/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).