[dpdk-dev] TX-packet counter increased when no packets were actually sent

Stefan Binna stefan.binna at salzburgresearch.at
Thu Aug 6 14:46:53 CEST 2015


I have created a little testbed for DPDK testing.

NIC: Intel Gigabit 82574L (1-port)

The testbed for DPDK has following structure:

1) al40-118 ( DUT running the DPDK application
2) al40-119 ( Used for sending traffic to al40-118
3) al40-111 ( Used to sniff the traffic send on the 

All three devices are connected via a hub and use the network

*Test:* Ping the DUT and review network traffic

At al40-119 an ARP-Table-Entry was created and the device al40-118 was 

arp -s 68:05:ca:37:51:75

On al40-118 the application testpmd was started with following parameters:

./x86_64-native-linuxapp-gcc/build/app/test-pmd/testpmd -c 0xf -n 4 -- -i --portmask=0x1 --nb-cores=2 --port-topology=chained

After start of the testpmd application the ports were started and after 
a while stopped:

start #wait a while due to testduration

What's interesting is, that the TX-packet counter in the output of the 
"stop" command had the same value as the RX-packet counter. But the 
actual traffic on the network sniffed with Wireshark only showed the 
ping request but never a response on any layer (not even L2).

Sample output of the "stop" command:

Telling cores to stop...
Waiting for lcores to finish...

   ---------------------- Forward statistics for port 0  ----------------------
   RX-packets: 2              RX-dropped: 0             RX-total: 2
   TX-packets: 2              TX-dropped: 0             TX-total: 2

   +++++++++++++++ Accumulated forward statistics for all ports+++++++++++++++
   RX-packets: 2              RX-dropped: 0             RX-total: 2
   TX-packets: 2              TX-dropped: 0             TX-total: 2

Stopping port 0...done

Could you tell me why the TX-packet counter increased when actually no 
packets were sent out to the network or in other words, 
where have the packets been sent out?
And is it even possible to set the same port for RX and TX?


Regards, Stefan.

More information about the dev mailing list