From: Dmitry Vyal <dmitryvyal@gmail.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] rte_malloc_socket UNABLE to allocate 8GB.
Date: Wed, 24 Sep 2014 19:26:35 +0400 [thread overview]
Message-ID: <5422E2AB.4070906@gmail.com> (raw)
Dear list,
I'm experiencing problems allocating big chunks of memory with
rte_malloc_socket. Basically, it successfully allocates 6GB but returns
NULL when I try to allocate 8GB. I tried dpdk-1.5.1 and 1.7.1 and got
similar behavior. First machine I was trying this on had 29*1GB
hugepages on single NUMA node, preallocated using grub. Another one had
14000*2Mb hugepages split between two sockets.
Are there any restrictions on maximum size of the block to be allocated
with rte_malloc_socket?
$ mount |grep hug
nodev on /mnt/huge type hugetlbfs (rw,pagesize=1Gb)
$ cat /sys/kernel/mm/hugepages/hugepages-1048576kB/nr_hugepages
29
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise
Best regards,
Dmitry
reply other threads:[~2014-09-24 15:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=5422E2AB.4070906@gmail.com \
--to=dmitryvyal@gmail.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).