From: Hossein Golestani <hosseing@umich.edu>
To: users@dpdk.org
Subject: [dpdk-users] tep_termination issue with memseg_list
Date: Wed, 1 May 2019 17:25:22 -0400 [thread overview]
Message-ID: <CAPtm8pR40VXAPJM6zOHsX1Sai50r9bHRjeBPszKeeY0yQnQuqQ@mail.gmail.com> (raw)
Hi,
I'm trying to run the tep_termination sample application. But I'm getting
the error message "couldn't find suitable memseg_list" when the application
wants to create the mbuf pool.
The command I use is:
$ sudo ./tep_termination -l 0-3 -n 4 --huge-dir /mnt/huge -w 0000:65:00.0
-- -p 0x1 --dev-basename tep-termination --nb-devices 4 --udp-port 4789
--filter-type 1
The complete log messages are as follows:
EAL: Detected 48 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: PCI device 0000:65:00.0 on NUMA socket 0
EAL: probe driver: 15b3:1017 net_mlx5
EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
EAL: eal_memalloc_alloc_seg_bulk(): couldn't find suitable memseg_list
EAL: Error - exiting with code: 1
Cause: Cannot create mbuf pool
(I also get that "No free hugepages..." message with other applications,
but it doesn't stop them from working.)
Hardware/software specifications of my system are as follows:
DPDK version: 18.11.1
gcc version: 7.3.0
OS: Ubuntu 18.04.2 LTS
CPU: Xeon Platinum 8160
NIC: Mellanox MCX556A-ECAT ConnectX-5
Please let me know if more information is needed. I'd really appreciate it
if some clues could be provided regarding this issue.
Thanks,
Hossein
reply other threads:[~2019-05-06 19:52 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=CAPtm8pR40VXAPJM6zOHsX1Sai50r9bHRjeBPszKeeY0yQnQuqQ@mail.gmail.com \
--to=hosseing@umich.edu \
--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).