From: "RAJESH KUMAR S.R" <rajuuu1992@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] [DPDK-PDUMP] Issue: RING: Cannot reserve memory
Date: Mon, 12 Mar 2018 15:55:00 +0530 [thread overview]
Message-ID: <CAC-BHbUAAZPE453tfCPoEo-K0o-L+ft_ev002eD46oi7oeh3DA@mail.gmail.com> (raw)
Hi,
I am new to dpdk.
I'm trying to use dpdk-pdump tool. I'm able to capture packets on dpdk
ports.
But, I'm facing the following issue
I'm getting a error "RING:Cannot reserve memory" while trying to restart
the pdump tool or running 2 instances of pdump.
I have also used the rte_eal_cleanup while exiting pdump main function.
Output:
* sudo /opt/pep/active/bin/dpdk-pdump -- --pdump
'port=0,queue=*,rx-dev=/tmp/rx.pcap,tx-dev=/tmp/tx.pcap'*
[sudo] password for admin:
EAL: Detected 2 lcore(s)
EAL: Multi-process socket /var/run/.rte_unix_1061_ce297dfe759
EAL: Probing VFIO support...
EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the
kernel.
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:04.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:05.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: Requested device 0000:00:05.0 cannot be used
PMD: Initializing pmd_pcap for net_pcap_rx_0
PMD: Creating pcap-backed ethdev on numa socket -1
Port 2 MAC: 00 00 00 01 02 03
PMD: Initializing pmd_pcap for net_pcap_tx_0
PMD: Creating pcap-backed ethdev on numa socket -1
Port 3 MAC: 00 00 00 01 02 03
^C
Signal 2 received, preparing to exit...
##### PDUMP DEBUG STATS #####
-packets dequeued: 4
-packets transmitted to vdev: 4
-packets freed: 0
Restarting........
*> sudo /opt/pep/active/bin/dpdk-pdump -- --pdump
'port=0,queue=*,rx-dev=/tmp/rx.pcap,tx-dev=/tmp/tx.pcap'*
EAL: Detected 2 lcore(s)
EAL: Multi-process socket /var/run/.rte_unix_1073_cea9cc51241
EAL: Probing VFIO support...
EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the
kernel.
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:04.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:05.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: Requested device 0000:00:05.0 cannot be used
PMD: Initializing pmd_pcap for net_pcap_rx_0
PMD: Creating pcap-backed ethdev on numa socket -1
PMD: Initializing pmd_pcap for net_pcap_tx_0
PMD: Creating pcap-backed ethdev on numa socket -1
Segmentation fault
*> sudo /opt/pep/active/bin/dpdk-pdump -- --pdump
'port=0,queue=*,rx-dev=/tmp/rx.pcap,tx-dev=/tmp/tx.pcap'*
EAL: Detected 2 lcore(s)
EAL: Multi-process socket /var/run/.rte_unix_1087_cec3ab006b1
EAL: Probing VFIO support...
EAL: WARNING: Address Space Layout Randomization (ASLR) is enabled in the
kernel.
EAL: This may cause issues with mapping memory into secondary processes
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable
clock cycles !
EAL: PCI device 0000:00:03.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:04.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: PCI device 0000:00:05.0 on NUMA socket -1
EAL: Invalid NUMA socket, default to 0
EAL: probe driver: 1af4:1000 net_virtio
EAL: Requested device 0000:00:05.0 cannot be used
RING: Cannot reserve memory
EAL: Error - exiting with code: 1
Cause: File exists:create_mp_ring_vdev:634
Hugepage info:
cat /proc/meminfo | grep Huge
AnonHugePages: 6144 kB
HugePages_Total: 300
HugePages_Free: 0
HugePages_Rsvd: 0
HugePages_Surp: 0
Hugepagesize: 2048 kB
Can you please help me in finding the issue.
Thanks,
Rajesh kumar S R
next reply other threads:[~2018-03-12 10:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-12 10:25 RAJESH KUMAR S.R [this message]
2018-03-17 15:58 ` Rosen, Rami
2018-03-18 17:52 ` RAJESH KUMAR S.R
2018-03-18 19:09 ` Rosen, Rami
2018-03-19 11:24 ` RAJESH KUMAR S.R
2018-03-20 9:25 ` RAJESH KUMAR S.R
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=CAC-BHbUAAZPE453tfCPoEo-K0o-L+ft_ev002eD46oi7oeh3DA@mail.gmail.com \
--to=rajuuu1992@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).