From: ikuzar RABE <ikuzar9295@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] dpdk-pdump does not work
Date: Fri, 7 Dec 2018 17:58:10 +0100 [thread overview]
Message-ID: <CACNnN_nx9qUXeGPQhFww_+mvPGfqU=6WSOWO6O=JZidHk4vRkA@mail.gmail.com> (raw)
Hi all,
I use dpdk on Linux Debian 8 to read packets from XL710 intel NIC and would
like to put them into a pcap file (capture.pcap) using dpdk-pdump
I replay packets from another machine. At the end of replay, I check the
size of captures.pcap. Its size is 0.
I tell dpdk-pdump to read from port 1. But it seems to read from port 2...
Does anyone know what goes wrong ?
here is how I proceeded, as indicated here
http://doc.dpdk.org/guides-18.11/howto/packet_capture_framework.html?highlight=pcap
:
1. I run testpmd: I see packets stats on port 1
2. I run dpdk-pdump: it does not dump packets
*testpmd:*
MY-DPDK:/opt/dpdk/dpdk-18.11# ./x86_64-native-linuxapp-gcc/app/testpmd -c
0xf0 -n 4 -- -i --port-topology=chained
EAL: Detected 12 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Probing VFIO support...
EAL: PCI device 0000:01:00.0 on NUMA socket 0
EAL: probe driver: 8086:10c9 net_e1000_igb
EAL: PCI device 0000:01:00.1 on NUMA socket 0
EAL: probe driver: 8086:10c9 net_e1000_igb
EAL: PCI device 0000:07:00.0 on NUMA socket 0
EAL: probe driver: 8086:10d3 net_e1000_em
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
Interactive-mode selected
testpmd: create a new mbuf pool <mbuf_pool_socket_0>: n=171456, size=2176,
socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
Configuring Port 0 (socket 0)
Port 0: 3C:FD:FE:CD:90:30
Configuring Port 1 (socket 0)
Port 1: 3C:FD:FE:CD:90:31
Checking link statuses...
Done
testpmd>
Port 1: link state change event
testpmd> show port stats 1
######################## NIC statistics for port 1
########################
RX-packets: 2035 RX-missed: 129333 RX-bytes: 10369023
RX-errors: 45
RX-nombuf: 0
TX-packets: 0 TX-errors: 0 TX-bytes: 0
Throughput (since last show)
Rx-pps: 12
Tx-pps: 0
############################################################################
*dpdk-pdump:*
MY-DPDK:/opt/dpdk/dpdk-18.11# ./x86_64-native-linuxapp-gcc/app/dpdk-pdump
-- --pdump 'port=1,queue=*,rx-dev=/tmp/capture.pcap'
EAL: Detected 12 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_11858_2708e10977042
EAL: Probing VFIO support...
EAL: PCI device 0000:01:00.0 on NUMA socket 0
EAL: probe driver: 8086:10c9 net_e1000_igb
EAL: PCI device 0000:01:00.1 on NUMA socket 0
EAL: probe driver: 8086:10c9 net_e1000_igb
EAL: PCI device 0000:07:00.0 on NUMA socket 0
EAL: probe driver: 8086:10d3 net_e1000_em
EAL: PCI device 0000:09:00.0 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
EAL: PCI device 0000:09:00.1 on NUMA socket 0
EAL: probe driver: 8086:1583 net_i40e
Port 2 MAC: 02 70 63 61 70 00
Thanks for your help,
ikuzar
reply other threads:[~2018-12-07 16:58 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='CACNnN_nx9qUXeGPQhFww_+mvPGfqU=6WSOWO6O=JZidHk4vRkA@mail.gmail.com' \
--to=ikuzar9295@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).