DPDK usage discussions
 help / color / mirror / Atom feed
From: Mridula V Gangadharan <mgangadhar@sandvine.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] i40evf: Problem with the statistics
Date: Mon, 4 Jun 2018 13:33:57 +0000	[thread overview]
Message-ID: <d35e90132dd8431a92285264058aa879@sandvine.com> (raw)

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

                 reply	other threads:[~2018-06-04 13:34 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d35e90132dd8431a92285264058aa879@sandvine.com \
    --to=mgangadhar@sandvine.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).