From: 廖書華 <sim860927@gmail.com>
To: users@dpdk.org
Cc: 林庭安 <lingwanjae@gmail.com>
Subject: Pdump Didn't capture the packet
Date: Mon, 15 Nov 2021 13:39:10 +0800 [thread overview]
Message-ID: <CANq=q43rnJEJf=cer5Z9Hg1aF6ZQFoa7NDuYd8YEzuRKH8fL2A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 3997 bytes --]
Dear all,
Currently, I want to use pdump to capture our DPDK application, however for
the pdump side, unfortunately, didn't capture any packet, also pdump didn't
print any error. While for our application, it also didn't print any log
related to pdump.
*- Here's the log of pdump*
[oran@localhost pdump]$ sudo ./dpdk-pdump --file-prefix wls_1 -- --pdump
'port=0,queue=*,tx-dev=/home/oran/Music/tx.pcap,rx-dev=/home/oran/Music/rx.pcap'
[sudo] password for oran: EAL: Detected 96 lcore(s) EAL: Detected 2 NUMA
nodes EAL: Multi-process socket
/var/run/dpdk/wls_1/mp_socket_9612_d352314e70d54 EAL: Selected IOVA mode
'VA' EAL: Probing VFIO support... EAL: VFIO support initialized EAL: PCI
device 0000:00:04.0 on NUMA socket 0 EAL: probe driver: 8086:2021
rawdev_ioat EAL: PCI device 0000:00:04.1 on NUMA socket 0 EAL: probe
driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:00:04.2 on NUMA socket 0
EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:00:04.3 on
NUMA socket 0 EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device
0000:00:04.4 on NUMA socket 0 EAL: probe driver: 8086:2021 rawdev_ioat EAL:
PCI device 0000:00:04.5 on NUMA socket 0 EAL: probe driver: 8086:2021
rawdev_ioat EAL: PCI device 0000:00:04.6 on NUMA socket 0 EAL: probe
driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:00:04.7 on NUMA socket 0
EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:18:00.0 on
NUMA socket 0 EAL: probe driver: 8086:1572 net_i40e EAL: PCI device
0000:18:00.1 on NUMA socket 0 EAL: probe driver: 8086:1572 net_i40e EAL:
PCI device 0000:18:0a.0 on NUMA socket 0 EAL: probe driver: 8086:154c
net_i40e_vf EAL: using IOMMU type 1 (Type 1) EAL: PCI device 0000:18:0a.1
on NUMA socket 0 EAL: probe driver: 8086:154c net_i40e_vf EAL: PCI device
0000:3d:00.0 on NUMA socket 0 EAL: probe driver: 8086:37d2 net_i40e EAL:
PCI device 0000:3d:00.1 on NUMA socket 0 EAL: probe driver: 8086:37d2
net_i40e EAL: PCI device 0000:80:04.0 on NUMA socket 1 EAL: probe driver:
8086:2021 rawdev_ioat EAL: PCI device 0000:80:04.1 on NUMA socket 1 EAL:
probe driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:80:04.2 on NUMA
socket 1 EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device
0000:80:04.3 on NUMA socket 1 EAL: probe driver: 8086:2021 rawdev_ioat EAL:
PCI device 0000:80:04.4 on NUMA socket 1 EAL: probe driver: 8086:2021
rawdev_ioat EAL: PCI device 0000:80:04.5 on NUMA socket 1 EAL: probe
driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:80:04.6 on NUMA socket 1
EAL: probe driver: 8086:2021 rawdev_ioat EAL: PCI device 0000:80:04.7 on
NUMA socket 1 EAL: probe driver: 8086:2021 rawdev_ioat Port 2 MAC: 02 70 63
61 70 00 Port 3 MAC: 02 70 63 61 70 01 core (0), capture for (1) tuples -
port 0 device ((null)) queue 65535 Primary process is no longer active,
exiting... EAL: failed to send to (/var/run/dpdk/wls_1/mp_socket) due to
Connection refused EAL: Fail to send request
/var/run/dpdk/wls_1/mp_socket:mp_pdump PDUMP: client request for pdump
enable/disable failed EAL: failed to send to
(/var/run/dpdk/wls_1/mp_socket) due to Connection refused EAL: Fail to send
request /var/run/dpdk/wls_1/mp_socket:eal_dev_mp_request EAL: Cannot send
request to primary EAL: Failed to send hotplug request to primary EAL:
failed to send to (/var/run/dpdk/wls_1/mp_socket) due to Connection refused
EAL: Fail to send request /var/run/dpdk/wls_1/mp_socket:eal_dev_mp_request
EAL: Cannot send request to primary EAL: Failed to send hotplug request to
primary ##### PDUMP DEBUG STATS ##### -packets dequeued: 0 -packets
transmitted to vdev: 0 -packets freed: 0
*- Here's the detailed step using pdump*
1. Add rte_pdump_init() and rte_pdump_uninit() to our application
2. Recompile DPDK 19.11
3. Add the library, -lrte_pdump & -lrte_pmd_pcap to our application's
Makefile
4. Bind the virtual function for DPDK port (vfio-pci)
Does I miss something? Or does pdump can not capture the virtual function
packet ?
I will be grateful for any help you can provide.
Best Regards,
Shu-hua, Liao
[-- Attachment #2: Type: text/html, Size: 5343 bytes --]
next reply other threads:[~2021-11-15 5:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 5:39 廖書華 [this message]
2021-11-15 8:57 ` Pattan, Reshma
2021-11-17 3:11 ` 廖書華
2021-11-17 10:01 ` Pattan, Reshma
2021-11-19 1:47 ` 廖書華
2021-11-19 5:23 ` 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='CANq=q43rnJEJf=cer5Z9Hg1aF6ZQFoa7NDuYd8YEzuRKH8fL2A@mail.gmail.com' \
--to=sim860927@gmail.com \
--cc=lingwanjae@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).