Dear,

Yes, for the pcap, it is empty.

I observe that on the pdump side, it will stuck in EAL: VFIO support initialized (red log below). After the primary application terminates, it will print the remaining log (blue log below). Is that normal ?

- 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

Best Regards,

Shu-hua, Liao

Pattan, Reshma <reshma.pattan@intel.com> 於 2021年11月17日週三下午6:01寫道：

From: 廖書華 <sim860927@gmail.com>
Sent: Wednesday, November 17, 2021 3:11 AM
To: Pattan, Reshma <reshma.pattan@intel.com>
Cc: users@dpdk.org
Subject: Re: Pdump Didn't capture the packet

Dear,

Thank you for the information !

I rerun the primary application with the other terminal running pdump, however it still can't capture the packet.

As for the logs you mentioned that is printed after the primary application terminates. Also, for the primary application log, I can make sure it transmits and receives the packet, but pdump still can't capture it.

[Reshma]: Are the pcap captured files empty? That might need some debugging I guess. When you stop the pdump application you should see below stats.

If you see 0 “packets dequeued”, that means there is no Packets received from primary to pdump application.

So, nee to debug the pdump library what is happening , why primary application packets are not send to pdump application. You can try to debugging the pdump library and pdump

application.

packets dequeued:



packets transmitted to vdev:



packets freed:

- For 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'

Also, do you know whether pdump can capture the virtual function packet or not ? (We bind to vfio-pci)

[Reshma]: I have not tested with VFs , I always used PFs.

Best Regards,

Shu-hua, Liao

Pattan, Reshma <reshma.pattan@intel.com> 於 2021年11月15日週一下午4:58寫道：

From: 廖書華 <sim860927@gmail.com>
Sent: Monday, November 15, 2021 5:39 AM
To: users@dpdk.org
Cc: 林庭安 <lingwanjae@gmail.com>
Subject: Pdump Didn't capture the packet

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'

<snip>

Primary process is no longer active, exiting...

[Reshma]: From this log it is clear that, primary application is not running. Rerun the primary application and in other terminal run the pdump application.

Best Regards,

Shu-hua, Liao