From: Marco Varlese <marco.varlese@suse.com>
To: "users@dpdk.org" <users@dpdk.org>, dev@dpdk.org
Subject: [dpdk-dev] Problem with MBUF pool allocation
Date: Mon, 12 Jun 2017 16:15:08 +0200 [thread overview]
Message-ID: <1497276908.3084.37.camel@suse.com> (raw)
Hi,
I'm seeing an error reported by the DPDK EAL when allocating the MBUF pools.
The error is:
"MBUF: error setting mempool handler"
I have a multi-node NUMA system and I get the exact same error when trying to
allocate the memory from the different nodes.
The bootstrap parameters I use to reserve huge-pages are:
"default_hugepagesz=1G hugepagesz=1G hugepages=32"
If I check the available huge-pages in my systems they look Ok (see below).
fromm:~/:[130]# cat /proc/meminfo
MemTotal: 263470432 kB
MemFree: 228408660 kB
MemAvailable: 227792692 kB
Buffers: 2148 kB
Cached: 229132 kB
SwapCached: 0 kB
Active: 113424 kB
Inactive: 150148 kB
Active(anon): 33508 kB
Inactive(anon): 1912 kB
Active(file): 79916 kB
Inactive(file): 148236 kB
Unevictable: 80 kB
Mlocked: 80 kB
SwapTotal: 2104316 kB
SwapFree: 2104316 kB
Dirty: 624 kB
Writeback: 0 kB
AnonPages: 33216 kB
Mapped: 60232 kB
Shmem: 2388 kB
Slab: 185240 kB
SReclaimable: 46320 kB
SUnreclaim: 138920 kB
KernelStack: 22592 kB
PageTables: 3000 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 117062316 kB
Committed_AS: 241992 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 0 kB
VmallocChunk: 0 kB
HardwareCorrupted: 0 kB
HugePages_Total: 32
HugePages_Free: 32
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 1048576 kB
DirectMap4k: 317756 kB
DirectMap2M: 11014144 kB
DirectMap1G: 258998272 kB
Any idea / help would be much appreciated.
Thanks,
Marco
next reply other threads:[~2017-06-12 14:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-12 14:15 Marco Varlese [this message]
2017-06-12 14:25 ` Bruce Richardson
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=1497276908.3084.37.camel@suse.com \
--to=marco.varlese@suse.com \
--cc=dev@dpdk.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).