Re: [dpdk-users] issues with dpdk-pdump

[Rami Rosen <roszenrami@gmail.com>]

Hi Srinivas,
Can you do a simple test to make sure your setup is ok ?
The suggested test is: instead od running you app, simply do the following:
First, bind a port to DPDK.
Then, run testpmd app (build/app/testpmd; as testpmd calls
rte_pdump_init() if RTE_LIBRTE_PDUMP is defined).
Then run again the dpdk-pdump, and post the result.
For me this works with dpdk-18.08, I am aware that you are using an
older version, but it should work also for you I believe.
Please note that I had to remove the while spaces in the command, but
anyhow these whitespaces did not
cause the error about rte_eal_config_attach() you had, but a parsing
error; after I removed these whitespaces, everything
was fine, no errors; what I actually ran is;
./build/app/dpdk-pdump --  --pdump
'port=0,queue=*,rx-dev=/work/rc.pcapng,tx-dev=/work/tc.pcapng'

and the log shows:

EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket_15023_7a49f061eb1
EAL: Probing VFIO support...
EAL: PCI device 0000:01:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 8086:1584 net_i40e
EAL: PCI device 0000:02:00.0 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 8086:1528 net_ixgbe
EAL: PCI device 0000:02:00.1 on NUMA socket -1
EAL:   Invalid NUMA socket, default to 0
EAL:   probe driver: 8086:1528 net_ixgbe
Port 2 MAC: 00 00 00 01 02 03
Port 3 MAC: 00 00 00 01 02 03


Regards,
Rami Rosen
http://ramirose.wixsite.com/ramirosen