DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Hayato Momma <h-momma@ce.jp.nec.com>
Subject: [dpdk-dev] [memnic PATCH 3/5] pmd: implement stats of MEMNIC
Date: Tue, 11 Mar 2014 05:38:49 +0000	[thread overview]
Message-ID: <7F861DC0615E0C47A872E6F3C5FCDDBD01073B19@BPXM14GP.gisp.nec.co.jp> (raw)

From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>

Implement missing feature to account statistics.
This patch adds just an infrastructure.

Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Reviewed-by: Hayato Momma <h-momma@ce.jp.nec.com>
---
 pmd/pmd_memnic.c | 45 ++++++++++++++++++++++++++++++++++++++++++---
 1 file changed, 42 insertions(+), 3 deletions(-)

diff --git a/pmd/pmd_memnic.c b/pmd/pmd_memnic.c
index bf5fc2e..fc2d990 100644
--- a/pmd/pmd_memnic.c
+++ b/pmd/pmd_memnic.c
@@ -51,6 +51,7 @@ struct memnic_adapter {
 	int up_idx, down_idx;
 	struct rte_mempool *mp;
 	struct ether_addr mac_addr;
+	struct rte_eth_stats stats[RTE_MAX_LCORE];
 };
 
 static inline struct memnic_adapter *get_adapter(const struct rte_eth_dev *dev)
@@ -126,13 +127,51 @@ static void memnic_dev_infos_get(struct rte_eth_dev *dev,
 	dev_info->max_mac_addrs = 1;
 }
 
-static void memnic_dev_stats_get(__rte_unused struct rte_eth_dev *dev,
-				 __rte_unused struct rte_eth_stats *stats)
+static void memnic_dev_stats_get(struct rte_eth_dev *dev,
+				 struct rte_eth_stats *stats)
 {
+	struct memnic_adapter *adapter = get_adapter(dev);
+	int i;
+
+	memset(stats, 0, sizeof(*stats));
+	for (i = 0; i < RTE_MAX_LCORE; i++) {
+		struct rte_eth_stats *st = &adapter->stats[i];
+
+		stats->ipackets += st->ipackets;
+		stats->opackets += st->opackets;
+		stats->ibytes += st->ibytes;
+		stats->obytes += st->obytes;
+		stats->ierrors += st->ierrors;
+		stats->oerrors += st->oerrors;
+		stats->imcasts += st->imcasts;
+		stats->rx_nombuf += st->rx_nombuf;
+		stats->fdirmatch += st->fdirmatch;
+		stats->fdirmiss += st->fdirmiss;
+
+		/* no multiqueue support now */
+		stats->q_ipackets[0] = st->q_ipackets[0];
+		stats->q_opackets[0] = st->q_opackets[0];
+		stats->q_ibytes[0] = st->q_ibytes[0];
+		stats->q_obytes[0] = st->q_obytes[0];
+		stats->q_errors[0] = st->q_errors[0];
+
+		stats->ilbpackets += st->ilbpackets;
+		stats->olbpackets += st->olbpackets;
+		stats->ilbbytes += st->ilbbytes;
+		stats->olbbytes += st->olbbytes;
+	}
 }
 
-static void memnic_dev_stats_reset(__rte_unused struct rte_eth_dev *dev)
+static void memnic_dev_stats_reset(struct rte_eth_dev *dev)
 {
+	struct memnic_adapter *adapter = get_adapter(dev);
+	int i;
+
+	for (i = 0; i < RTE_MAX_LCORE; i++) {
+		struct rte_eth_stats *st = &adapter->stats[i];
+
+		memset(st, 0, sizeof(*st));
+	}
 }
 
 static int memnic_dev_link_update(struct rte_eth_dev *dev,
-- 
1.8.4

             reply	other threads:[~2014-03-11  5:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11  5:38 Hiroshi Shimamoto [this message]
2014-03-24 15:25 ` Thomas Monjalon
2014-03-25  8:23   ` Hiroshi Shimamoto
2014-03-25 15:00     ` Thomas Monjalon

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=7F861DC0615E0C47A872E6F3C5FCDDBD01073B19@BPXM14GP.gisp.nec.co.jp \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=dev@dpdk.org \
    --cc=h-momma@ce.jp.nec.com \
    /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).