Dear Reshma,
Thanks for your kind response ! Unfortunately, it still can't work.
1) I double checked the return value (int) of these two functions, both of them return 0.
2) About the DPDK building, we are not using the shared library build.
3) For the primary side, I saw the log showed "-w 0000:00:00.0", which are the input of function rte_eal_init(). Therefore, I also tried to parse "-w 0000:00:00.0" on pdump side, however, it still got the error.
- Log in pdump side
- Log in primary side (Red font I think is related to DPDK)
---------------------
P.S 1. On primary side, If we change "-w 0000:00:00.0" to "-w 0000:86:02.0 -w 0000:86:02.1" which is the two bus-info we bind for DPDK.
We will get the error EAL: Failed to attach device on primary process, do you have any idea what is the root cause of this issue ?
xran_ethdi_init_dpdk_io: Calling rte_eal_init:wls_0 -c 0x2000021 -n2 --iova-mode=pa --socket-mem=8192 --socket-limit=8192 --proc-type=auto --file-prefix wls_0 -w 0000:86:02.0 -w 0000:86:02.1
EAL: Detected 40 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: Auto-detected process type: PRIMARY
EAL: Multi-process socket /var/run/dpdk/wls_0/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: PCI device 0000:86:02.0 on NUMA socket 1
EAL: probe driver: 8086:154c net_i40e_vf
EAL: using IOMMU type 1 (Type 1)
EAL: PCI device 0000:86:02.1 on NUMA socket 1
EAL: probe driver: 8086:154c net_i40e_vf
Return value (int) of rte_pdump_init() : 0
EAL: PCI device 0000:86:02.0 on NUMA socket 1
EAL: Failed to attach device on primary process
initializing port 0 for TX, drv=net_i40e_vf
Port 0 MAC: 00 11 22 33 44 66
Port 0: nb_rxd 4096 nb_txd 4096
Checking link status portid [0] ... done
Port 0 Link Up - speed 10000 Mbps - full-duplex
EAL: PCI device 0000:86:02.1 on NUMA socket 1
EAL: Failed to attach device on primary process
initializing port 1 for TX, drv=net_i40e_vf
Port 1 MAC: 00 11 22 33 44 66
Port 1: nb_rxd 4096 nb_txd 4096
Checking link status portid [1] ... done
Port 1 Link Up - speed 10000 Mbps - full-duplex
vf 0 local SRC MAC: 00 11 22 33 44 66
vf 0 remote DST MAC: 00 11 22 33 44 55
vf 1 local SRC MAC: 00 11 22 33 44 66
vf 1 remote DST MAC: 00 11 22 33 44 55
P.S. 2 : For the DPDK environment we to build, we select x86_64-native-linuxapp-icc and Insert VFIO module.
Best Regards,
Shu-hua, Liao
> -----Original Message-----
> From: 廖書華 <sim860927@gmail.com>
> Yes, I already set *CONFIG_RTE_LIBRTE_PMD_PCAP=y *and
> *CONFIG_RTE_LIBRTE_PDUMP=y *in the file "dpdk-
> 19.11/config/common_base"
> then build DPDK.
> Also, in the files "dpdk-19.11/x86_64-native-linuxapp-icc/.config" and "dpdk-
> 19.11/x86_64-native-linuxapp-icc/.config.orig", they also show that
> *CONFIG_RTE_LIBRTE_PMD_PCAP=y *and *CONFIG_RTE_LIBRTE_PDUMP=y.*
>
> It seems that it already enabled pcap PMD of DPDK.
> Do you have other suggestions ?
Hi,
Few options you can double check
1)Make sure your primary application is calling rte_pdump_init()/ret_pudmp_uninit() to initialize/uninitialize the pdump library.
2)If you are using a shared library build, double check you are linking pcap pmd properly in primary build as explained in below link
https://www.mail-archive.com/users@dpdk.org/msg05039.html
https://stackoverflow.com/questions/62795017/dpdk-pdump-failed-to-hotplug-add-device
3)If you are passing any pci device using eal "-w" option to primary, try to pass the same device to secondary also using "-w" option .
If you still see the issue please paste the full primary and secondary application run log with command that you are running.
Also what kind of build you are using.
Thanks,
Reshma