From: Jay Rolette <rolette@infiniteio.com>
To: "Damjan Marion (damarion)" <damarion@cisco.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] mmap fails with more than 40000 hugepages
Date: Thu, 5 Feb 2015 07:22:51 -0600 [thread overview]
Message-ID: <CADNuJVqipnD2yBojhMxuzLxHDtr6FdQKzmihReaMm500htORpA@mail.gmail.com> (raw)
In-Reply-To: <736BD68D-C5DF-4883-A720-DAD8A2A866BE@cisco.com>
On Thu, Feb 5, 2015 at 6:00 AM, Damjan Marion (damarion) <damarion@cisco.com
> wrote:
> Hi,
>
> I have system with 2 NUMA nodes and 256G RAM total. I noticed that DPDK
> crashes in rte_eal_init()
> when number of available hugepages is around 40000 or above.
> Everything works fine with lower values (i.e. 30000).
>
> I also tried with allocating 40000 on node0 and 0 on node1, same crash
> happens.
>
>
> Any idea what might be causing this?
>
Any reason you can't switch to using 1GB hugepages? You'll get better
performance and your init time will be shorter. The systems we run on are
similar (256GB, 2 NUMA nodes) and that works fine for us.
Not directly related, but if you have to stick with 2MB hugepages, you
might want to take a look at a patch I submitted that fixes the O(n^2)
algorithm used in initializing hugepages.
Jay
next prev parent reply other threads:[~2015-02-05 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 12:00 Damjan Marion (damarion)
2015-02-05 12:59 ` Neil Horman
2015-02-05 13:20 ` Damjan Marion (damarion)
2015-02-05 14:59 ` Neil Horman
2015-02-05 15:41 ` Damjan Marion (damarion)
2015-02-05 16:35 ` Neil Horman
2015-02-05 13:22 ` Jay Rolette [this message]
2015-02-05 13:36 ` Damjan Marion (damarion)
2015-02-05 15:09 ` Jay Rolette
2015-02-06 1:46 ` Linhaifeng
2015-02-06 2:04 ` Linhaifeng
2015-02-06 10:26 ` De Lara Guarch, Pablo
2015-02-06 10:31 ` Damjan Marion (damarion)
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=CADNuJVqipnD2yBojhMxuzLxHDtr6FdQKzmihReaMm500htORpA@mail.gmail.com \
--to=rolette@infiniteio.com \
--cc=damarion@cisco.com \
--cc=dev@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).