From: Maryam Tahhan <maryam.tahhan@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 1/1] ethdev: distinguish between drop and error stats
Date: Mon, 19 Oct 2015 13:20:53 +0100 [thread overview]
Message-ID: <1445257253-3673-1-git-send-email-maryam.tahhan@intel.com> (raw)
Make a distniction between dropped packets and error statistics to allow
a higher level fault management entity to interact with DPDK and take
appropriate measures when errors are detected. It will also provide
valuable information for any applications that collects/extracts DPDK
stats, such applications include Open vSwitch.
After this patch the distinction is:
ierrors = Total number of packets dropped by hardware (malformed
packets, ...) Where the # of drops can ONLY be <= the packets received
(without overlap between registers).
ipkterrors = Total number of erroneous received packets. Where the #
of errors can be >= the packets received (without overlap between
registers), this is because there may be multiple errors associated with
a packet.
v2:
- Added detailed descriptions for ierrors and ipkterrors.
Signed-off-by: Maryam Tahhan <maryam.tahhan@intel.com>
---
lib/librte_ether/rte_ethdev.h | 12 +++++++++++-
1 file changed, 11 insertions(+), 1 deletion(-)
diff --git a/lib/librte_ether/rte_ethdev.h b/lib/librte_ether/rte_ethdev.h
index 8a8c82b..e27ba31 100644
--- a/lib/librte_ether/rte_ethdev.h
+++ b/lib/librte_ether/rte_ethdev.h
@@ -200,8 +200,18 @@ struct rte_eth_stats {
/**< Deprecated; Total of RX packets with CRC error. */
uint64_t ibadlen;
/**< Deprecated; Total of RX packets with bad length. */
- uint64_t ierrors; /**< Total number of erroneous received packets. */
+ uint64_t ierrors;
+ /**< Total number of packets dropped by hardware (malformed packets...)
+ * Where the # of drops can ONLY be <= the packets received (without
+ * overlap between registers).
+ */
uint64_t oerrors; /**< Total number of failed transmitted packets. */
+ uint64_t ipkterrors;
+ /**< Total number of erroneous received packets. Where the number of
+ * errors can be >= the packets received (without overlap between
+ * registers), this is because there may be multiple errors associated with
+ * a packet.
+ */
uint64_t imcasts;
/**< Deprecated; Total number of multicast received packets. */
uint64_t rx_nombuf; /**< Total number of RX mbuf allocation failures. */
--
2.4.3
next reply other threads:[~2015-10-19 12:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 12:20 Maryam Tahhan [this message]
2015-11-02 23:46 ` Thomas Monjalon
2015-11-03 13:14 ` Tahhan, Maryam
2015-11-03 13:55 ` Thomas Monjalon
2015-11-03 14:56 ` Tahhan, Maryam
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=1445257253-3673-1-git-send-email-maryam.tahhan@intel.com \
--to=maryam.tahhan@intel.com \
--cc=dev@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).