From: Don Trotter <djtrotter@yahoo.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: Re: EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
Date: Thu, 7 Sep 2023 19:58:35 +0000 (UTC) [thread overview]
Message-ID: <1630438817.5159600.1694116715543@mail.yahoo.com> (raw)
In-Reply-To: <2101629309.5133186.1694112839948@mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 2062 bytes --]
To clarify, the log message when my application called rte_mempool_create() to create the "node_pool", and the call succeeded.
Thanks,Don Trotter
On Thursday, September 7, 2023 at 01:54:08 PM CDT, Don Trotter <djtrotter@yahoo.com> wrote:
Hi,
I have recently started using DPDK. I am working on a project on OcteonTX2 with DPDK 11.23.01. I am seeing this message from EAL during EAL init, but everything is working.
EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
The system has 96GB of memory. These 2 pools get created and everything works fine.
mempool <mbuf_pool>@0x13fed3e00 flags=10 socket_id=0 pool=0x1140300000 iova=0x13fed3e00 nb_mem_chunks=1 size=65535 populated_size=65535 header_size=128 elt_size=10200 trailer_size=40 total_obj_size=10368 private_data_size=128 ops_index=0 ops_name: <cn9k_mempool_ops> avg bytes/object=10368.558602
mempool <node_pool>@0x1575d8180 flags=10 socket_id=-1 pool=0x19ffffd00 iova=0x1575d8180 nb_mem_chunks=2 size=134217727 populated_size=134217727 header_size=128 elt_size=256 trailer_size=0 total_obj_size=384 private_data_size=0 ops_index=3 ops_name: <ring_mp_mc> avg bytes/object=384.000094
You read that right. I’ve got 128*1024*1024 256 byte buffers created for data.
I also see there is still heap left, although pretty low after.
Heap id:0 Heap name:socket_0 Heap_size:55834574848, Free_size:2403644544, Alloc_size:53430930304, Greatest_free_size:536870016, Alloc_count:293, Free_count:5,
Linux free stats.
tmp# free -h -w total used free shared buffers cache availableMem: 95Gi 88Gi 6.5Gi 444Mi 0B 470Mi 599MiSwap: 0B 0B 0B
Is there anything wrong with that EAL log? Is there a lurking problem?
Thanks,Don Trotter
[-- Attachment #2: Type: text/html, Size: 4495 bytes --]
next prev parent reply other threads:[~2023-09-07 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2101629309.5133186.1694112839948.ref@mail.yahoo.com>
2023-09-07 18:53 ` Don Trotter
2023-09-07 19:58 ` Don Trotter [this message]
2023-09-07 20:21 ` Stephen Hemminger
2023-09-07 21:33 ` Don Trotter
2023-09-08 2:26 jiangheng (G)
2023-09-08 14:31 ` Don Trotter
2023-09-08 21:03 ` Stephen Hemminger
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=1630438817.5159600.1694116715543@mail.yahoo.com \
--to=djtrotter@yahoo.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).