[dpdk-dev] i40evf: Problem with the statistics

[dpdk-dev] i40evf: Problem with the statistics

[Mridula V Gangadharan]

Hi,

I am testing packet drops scenario by setting the MTU size.
My setup have i40evf driver. I set the dpdk interface's MTU size to 1800.
I am sending 100 packets of size 1918 each.
I am expecting the drop counter to increment.
rte_eth_stats_get() returns i.packets with number of packets I sent.
There are no drop counters incrementing. Also my application is not recieving any packets.
Is there some issue with dpdk statistics?
xstats  output is as follows. It is not showing any drops but rx_good_bytes counts are incrementing.

####################################################

NIC extended statistics for port 1
####################################################
rx_good_packets: 656
tx_good_packets: 556
rx_good_bytes: 225160
tx_good_bytes: 33360
rx_errors: 0
tx_errors: 0
rx_mbuf_allocation_errors: 0
rx_q0packets: 0
rx_q0bytes: 0
rx_q0errors: 0
tx_q0packets: 0
tx_q0bytes: 0
rx_bytes: 225160
rx_unicast_packets: 656
rx_multicast_packets: 0
rx_broadcast_packets: 0
rx_dropped_packets: 0
rx_unknown_protocol_packets: 0
tx_bytes: 33360
tx_unicast_packets: 556
tx_multicast_packets: 0
tx_broadcast_packets: 0
tx_dropped_packets: 0
tx_error_packets: 0

Thanks and Regards,
Mridula

[dpdk-dev] i40evf: Problem with the statistics

[Mridula V Gangadharan]

Hi,

I am testing packet drops scenario by setting the MTU size. 
My setup have i40evf driver. I set the dpdk interface's MTU size to 1800. 
I am sending 100 packets of size 1918 each.
I am expecting the drop counter to increment.
rte_eth_stats_get() returns i.packets with number of packets I sent. 
There are no drop counters incrementing. Also my application is not recieving any packets.
Is there some issue with dpdk statistics?
xstats  output is as follows. It is not showing any drops but rx_good_bytes counts are incrementing.

####################################################

NIC extended statistics for port 1
####################################################
rx_good_packets: 656
tx_good_packets: 556
rx_good_bytes: 225160 
tx_good_bytes: 33360
rx_errors: 0
tx_errors: 0
rx_mbuf_allocation_errors: 0
rx_q0packets: 0
rx_q0bytes: 0
rx_q0errors: 0
tx_q0packets: 0
tx_q0bytes: 0
rx_bytes: 225160
rx_unicast_packets: 656
rx_multicast_packets: 0
rx_broadcast_packets: 0
rx_dropped_packets: 0
rx_unknown_protocol_packets: 0
tx_bytes: 33360
tx_unicast_packets: 556
tx_multicast_packets: 0
tx_broadcast_packets: 0
tx_dropped_packets: 0
tx_error_packets: 0

Thanks and Regards,
Mridula

[dpdk-dev] i40evf: Problem with the statistics

[Mridula V Gangadharan]

Hi,

I am testing packet drops scenario by setting the MTU size.
My setup have i40evf driver. I set the dpdk interface's MTU size to 1800.
I am sending 100 packets of size 1918 each.
I am expecting the drop counter to increment.
rte_eth_stats_get() returns i.packets with number of packets I sent.
There are no drop counters incrementing. Also my application is not recieving any packets.
Is there some issue with dpdk statistics?
xstats  output is as follows. It is not showing any drops but rx_good_bytes counts are incrementing.

####################################################

NIC extended statistics for port 1
####################################################
rx_good_packets: 656
tx_good_packets: 556
rx_good_bytes: 225160
tx_good_bytes: 33360
rx_errors: 0
tx_errors: 0
rx_mbuf_allocation_errors: 0
rx_q0packets: 0
rx_q0bytes: 0
rx_q0errors: 0
tx_q0packets: 0
tx_q0bytes: 0
rx_bytes: 225160
rx_unicast_packets: 656
rx_multicast_packets: 0
rx_broadcast_packets: 0
rx_dropped_packets: 0
rx_unknown_protocol_packets: 0
tx_bytes: 33360
tx_unicast_packets: 556
tx_multicast_packets: 0
tx_broadcast_packets: 0
tx_dropped_packets: 0
tx_error_packets: 0

Thanks and Regards,
Mridula


Disclaimer:
This communication (including any attachments) is intended for the use of the intended recipient(s) only and may contain information that is considered confidential, proprietary, sensitive and/or otherwise legally protected. Any unauthorized use or dissemination of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by return e-mail message and delete all copies of the original communication. Thank you for your cooperation.