From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mridula V Gangadharan Subject: i40evf: Problem with the statistics Date: Wed, 30 May 2018 13:56:21 +0000 Message-ID: <8ba4149fd8db42d9820e3d732827147d@sandvine.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable To: "dev@dpdk.org" Return-path: Received: from mail1.sandvine.com (Mail1.sandvine.com [64.7.137.134]) by dpdk.org (Postfix) with ESMTP id D10D734F3 for ; Wed, 30 May 2018 15:56:27 +0200 (CEST) Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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 recievi= ng 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 t= he intended recipient(s) only and may contain information that is considere= d confidential, proprietary, sensitive and/or otherwise legally protected. = Any unauthorized use or dissemination of this communication is strictly pro= hibited. If you have received this communication in error, please immediate= ly notify the sender by return e-mail message and delete all copies of the = original communication. Thank you for your cooperation.