[dpdk-users] Capture traffic with DPDK-dump

Pattan, Reshma reshma.pattan at intel.com
Thu Nov 10 11:56:26 CET 2016


Comments below.


> -----Original Message-----
> From: users [mailto:users-bounces at dpdk.org] On Behalf Of jose suarez
> Sent: Monday, November 7, 2016 5:50 PM
> To: users at dpdk.org
> Subject: [dpdk-users] Capture traffic with DPDK-dump
> Hello everybody!
> I am new in DPDK. I'm trying simply to capture traffic from a 10G physical
> NIC. I installed the DPDK from source files and activated the following
> modules in common-base file:
> Then I built the distribution using the dpdk-setup.h script. Also I add
> hugepages and check they are configured successfully:
> AnonHugePages:      4096 kB
> HugePages_Total:    2048
> HugePages_Free:        0
> HugePages_Rsvd:        0
> HugePages_Surp:        0
> Hugepagesize:       2048 kB
> To capture the traffic I guess I can use the dpdk-pdump application, but I
> don't know how to use it. First of all, does it work if I bind the interfaces
> using the uio_pci_generic drive? I guess that if I capture the traffic using the
> linux kernel driver (ixgbe) I will loose a lot of packets.
> To bind the NIC I write this command:
> sudo ./tools/dpdk-devbind.py --bind=uio_pci_generic eth0
> When I check the interfaces I can see that the NIC was binded successfully.
> Also I checked that mi NIC is compatible with DPDK (Intel
> 8599)
> Network devices using DPDK-compatible driver
> ============================================
> 0000:01:00.0 '82599ES 10-Gigabit SFI/SFP+ Network Connection'
> drv=uio_pci_generic unused=ixgbe,vfio-pci
> To capture packets, I read in the mailing list that it is necessary to run the
> testpmd application and then dpdk-pdump using different cores.
> So I used the following commands:
> sudo ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x6 -n 4 -- -i
> sudo ./x86_64-native-linuxapp-gcc/app/dpdk-pdump -c 0xff -n 2 -- --pdump
> 'device_id=01:00.0,queue=*,rx-dev=/tmp/file.pcap'

1)Please pass on the full PCI id, i.e "0000:01:00.0" in the command instead of "01:00.0".
In latest DPDK 16.11 code  full PCI id is used by eal layer to identify the device. 

2)Also note that you should not use same core mask for both primary and secondary processes in multi process context.
ex: -c0x6 for testpmd and -c0x2 for dpdk-pdump can be used. 

Please let me know how you are proceeding.


More information about the users mailing list