From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [Bug 1280] rte_mempool_create returning error "EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list"
Date: Fri, 25 Aug 2023 13:12:05 +0000 [thread overview]
Message-ID: <bug-1280-3@http.bugs.dpdk.org/> (raw)
[-- Attachment #1: Type: text/plain, Size: 3122 bytes --]
https://bugs.dpdk.org/show_bug.cgi?id=1280
Bug ID: 1280
Summary: rte_mempool_create returning error "EAL:
eal_memalloc_alloc_seg_bulk(): couldn't find suitable
memseg_list"
Product: DPDK
Version: 21.11
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: major
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: pingtosiva@gmail.com
Target Milestone: ---
Created attachment 258
--> https://bugs.dpdk.org/attachment.cgi?id=258&action=edit
proc/pid/maps output
Spawned a VM with RAM of 188GB and configured Huge page size as 1GB and number
of huge pages as 100. When tried to allocate mempool using rte_mempool_create
from testpmd process, after allocating 64 huge pages this call returns below
error message,
"EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list"
Though there were 35 huge pages available, mempool creation was failed.
The below call would create 1 huge page,
rte_mempool_create("test6", 1048576, 4096, 512, 0, 0, 0, 0, 0,
(int)rte_socket_id(), 0)
after creating 64 huge pages, this call started to fail. This fails even after
tweak the number of pool, element size etc.,
Appreciate if any help on this.
Details
========
Issue Platforms: ESXi, cn98xx
Huge page Size: 1 GB
number of Huge pages: 100
Command output
===============
gigamon@gigavue-vseries-node:~$ cat /proc/meminfo
MemTotal: 197867396 kB
MemFree: 91528492 kB
MemAvailable: 91268008 kB
Buffers: 84376 kB
Cached: 722624 kB
SwapCached: 0 kB
Active: 331440 kB
Inactive: 646316 kB
Active(anon): 1316 kB
Inactive(anon): 170872 kB
Active(file): 330124 kB
Inactive(file): 475444 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 0 kB
Writeback: 0 kB
AnonPages: 170764 kB
Mapped: 170252 kB
Shmem: 1432 kB
KReclaimable: 58308 kB
Slab: 104180 kB
SReclaimable: 58308 kB
SUnreclaim: 45872 kB
KernelStack: 3312 kB
PageTables: 3392 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 46402496 kB
Committed_AS: 701964 kB
VmallocTotal: 34359738367 kB
VmallocUsed: 23732 kB
VmallocChunk: 0 kB
Percpu: 1296 kB
HardwareCorrupted: 0 kB
AnonHugePages: 0 kB
ShmemHugePages: 0 kB
ShmemPmdMapped: 0 kB
FileHugePages: 0 kB
FilePmdMapped: 0 kB
HugePages_Total: 100
HugePages_Free: 36
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 1048576 kB
Hugetlb: 105062400 kB
DirectMap4k: 143232 kB
DirectMap2M: 4050944 kB
DirectMap1G: 199229440 kB
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #2: Type: text/html, Size: 5192 bytes --]
next reply other threads:[~2023-08-25 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 13:12 bugzilla [this message]
2023-08-28 17:39 ` bugzilla
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=bug-1280-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).