From: topperxin <topperxin@126.com>
To: "users@dpdk.org" <users@dpdk.org>, topperxin <topperxin@126.com>
Subject: [dpdk-users] eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
Date: Wed, 12 May 2021 16:47:14 +0800 (CST) [thread overview]
Message-ID: <2e51d58e.479b.1795fc237a4.Coremail.topperxin@126.com> (raw)
Hi list
For the dpdk 20.11
When I try to run helloworld example, like below:
./build/helloworld-static --socket-mem=100000,100000
I will get error like below:
EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
EAL: FATAL: Cannot init memory
EAL: Cannot init memory
PANIC in main():
Cannot init EAL
5: [./build/helloworld-static() [0x409f69]]
4: [/usr/lib64/libc.so.6(__libc_start_main+0xf5) [0x7fd70f8693d5]]
3: [./build/helloworld-static() [0x40a147]]
2: [./build/helloworld-static() [0x31337dd]]
1: [./build/helloworld-static() [0x315e5ff]]
Aborted (core dumped)
I have enough memory left for dpdk, like below:
HugePages_Total: 360
HugePages_Free: 360
HugePages_Rsvd: 0
HugePages_Surp: 0
Anyone has ever met this trouble? How to resolve this problem ? Any tips welcome.
Thanks a lot.
reply other threads:[~2021-05-12 8:47 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=2e51d58e.479b.1795fc237a4.Coremail.topperxin@126.com \
--to=topperxin@126.com \
--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).