From: Varun Lakkur <lakkurvarun@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Packets beyond MTU size in i40evf
Date: Wed, 6 Jun 2018 20:29:55 +0530 [thread overview]
Message-ID: <CAMx4k_RPmD_6B+QdbBbOnaxgL0tDfhcgabes=fh8rMb462cV3g@mail.gmail.com> (raw)
Hey,
I am using rte_eth_stats_get() to get the stats of how many packets
are received/transmitted by my application.
I am running SRIOV on XL710 (using i40evf pmd). When I send packets
beyond the MTU size, my application does not receive them as expected.
But these are not reported in rx_dropped_packets/rx_errors. I see that
these are counted as rx_good_packets. How do I differentiate the
oversized packets and count them correctly? Shouldn't they be counted
under rx_dropped_packets?
I went through the source code for i40e_dev_stats_get and
i40evf_dev_stats_get. I see that i40e reads extra counters from
i40e_hw_port_stats. Is there anything similar for SRIOV interfaces?
Here is the xstats counters I got from dpdk-procinfo:
####################################################
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
Regards,
Varun
reply other threads:[~2018-06-06 14:59 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='CAMx4k_RPmD_6B+QdbBbOnaxgL0tDfhcgabes=fh8rMb462cV3g@mail.gmail.com' \
--to=lakkurvarun@gmail.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).