From: Pavan Kumar <cspavanckm@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] EAL hugetables initialisation with 2 NUMA nodes broken in 18.08
Date: Tue, 9 Apr 2019 10:22:23 +0530 [thread overview]
Message-ID: <CAO4JN_BQPMQ8OkpP1+zmkg8GBzHc=HbiqkTFWJ7GMAWAXG6bGA@mail.gmail.com> (raw)
Hi,
I have a centos VM running on ESXi 6.7 server. VM CPU is configured with
only one physical socket. 2 NUMA nodes are detected based on the number of
CPU assigned to the VM. Prior to 18.08 when 2 NUMA nodes were detected
hugetable initialisation worked fine. With 18.08 it fails. Below is a snap
shot of the error. Kindly help me resolve this issue.
./myapp --log-level=eal,8 --legacy-mem -c 0x3fc00 -n 1 -b 0000:01:00.0 --
-M0xffff -s0xc00 -f0x1f000 -p0x3 --config
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 4 on socket 0
EAL: Detected lcore 5 as core 5 on socket 0
EAL: Detected lcore 6 as core 6 on socket 0
EAL: Detected lcore 7 as core 7 on socket 0
EAL: Detected lcore 8 as core 8 on socket 0
EAL: Detected lcore 9 as core 0 on socket 1
EAL: Detected lcore 10 as core 1 on socket 1
EAL: Detected lcore 11 as core 2 on socket 1
EAL: Detected lcore 12 as core 3 on socket 1
EAL: Detected lcore 13 as core 4 on socket 1
EAL: Detected lcore 14 as core 5 on socket 1
EAL: Detected lcore 15 as core 6 on socket 1
EAL: Detected lcore 16 as core 7 on socket 1
EAL: Detected lcore 17 as core 8 on socket 1
EAL: Support maximum 64 logical core(s) by configuration.
EAL: Detected 18 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Module /sys/module/vfio_pci not found! error 2 (No such file or
directory)
EAL: VFIO PCI modules not loaded
EAL: Probing VFIO support...
EAL: Module /sys/module/vfio not found! error 2 (No such file or directory)
EAL: VFIO modules not loaded, skipping VFIO support...
EAL: Ask a virtual area of 0x2e000 bytes
EAL: Virtual area found at 0x7faaeeb3a000 (size = 0x2e000)
EAL: Setting up physically contiguous memory...
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x7faaeead9000 (size = 0x61000)
EAL: Memseg list allocated: 0x800kB at socket 0
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x7fa6eb000000 (size = 0x400000000)
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x7faaeea78000 (size = 0x61000)
EAL: Memseg list allocated: 0x800kB at socket 0
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x7fa2eae00000 (size = 0x400000000)
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x7faaeea17000 (size = 0x61000)
EAL: Memseg list allocated: 0x800kB at socket 0
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x7f9eeac00000 (size = 0x400000000)
EAL: Ask a virtual area of 0x61000 bytes
EAL: Virtual area found at 0x7faaee9b6000 (size = 0x61000)
EAL: Memseg list allocated: 0x800kB at socket 0
EAL: Ask a virtual area of 0x400000000 bytes
EAL: Virtual area found at 0x7f9aeaa00000 (size = 0x400000000)
EAL: Requesting 352 pages of size 2MB from socket 0
EAL: Requesting 352 pages of size 2MB from socket 1
EAL: Attempting to map 8M on socket 0
EAL: Allocated 8M on socket 0
EAL: Attempting to map 696M on socket 0
EAL: Allocated 696M on socket 0
EAL: Attempting to map 2M on socket 1
EAL: Could not find space for memseg. Please increase
CONFIG_RTE_MAX_MEMSEG_PER_TYPE and/or CONFIG_RTE_MAX_MEM_PER_TYPE in
configuration.
EAL: Couldn't remap hugepage files into memseg lists
EAL: FATAL: Cannot init memory
EAL: Cannot init memory
EAL: Error - exiting with code: 1
Cause: Could not initialise EAL (-1)5:
Regards
Pavan Kumar C S
reply other threads:[~2019-04-09 13:02 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='CAO4JN_BQPMQ8OkpP1+zmkg8GBzHc=HbiqkTFWJ7GMAWAXG6bGA@mail.gmail.com' \
--to=cspavanckm@gmail.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).