From: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v2 01/10] table: added structure for storing table stats
Date: Thu, 30 Apr 2015 14:14:29 +0200 [thread overview]
Message-ID: <1430396078-968-2-git-send-email-michalx.k.jastrzebski@intel.com> (raw)
In-Reply-To: <1430396078-968-1-git-send-email-michalx.k.jastrzebski@intel.com>
From: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
Added common structure for table statistics.
Signed-off-by: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
---
lib/librte_table/rte_table.h | 25 +++++++++++++++++++++++++
1 file changed, 25 insertions(+)
diff --git a/lib/librte_table/rte_table.h b/lib/librte_table/rte_table.h
index d57bc33..9860b7b 100644
--- a/lib/librte_table/rte_table.h
+++ b/lib/librte_table/rte_table.h
@@ -58,6 +58,12 @@ extern "C" {
#include <rte_mbuf.h>
#include <rte_port.h>
+/** Lookup table statistics */
+struct rte_table_stats {
+ uint64_t n_pkts_in;
+ uint64_t n_pkts_lookup_miss;
+};
+
/**
* Lookup table create
*
@@ -186,6 +192,24 @@ typedef int (*rte_table_op_lookup)(
uint64_t *lookup_hit_mask,
void **entries);
+/**
+ * Lookup table stats read
+ *
+ * @param port
+ * Handle to lookup table instance
+ * @param stats
+ * Handle to table stats struct to copy data
+ * @param clear
+ * Flag indicating that stats should be cleared after read
+ *
+ * @return
+ * Error code or 0 on success.
+ */
+typedef int (*rte_table_op_stats_read)(
+ void *table,
+ struct rte_table_stats *stats,
+ int clear);
+
/** Lookup table interface defining the lookup table operation */
struct rte_table_ops {
rte_table_op_create f_create; /**< Create */
@@ -193,6 +217,7 @@ struct rte_table_ops {
rte_table_op_entry_add f_add; /**< Entry add */
rte_table_op_entry_delete f_delete; /**< Entry delete */
rte_table_op_lookup f_lookup; /**< Lookup */
+ rte_table_op_stats_read f_stats; /**< Stats */
};
#ifdef __cplusplus
--
1.7.9.5
next prev parent reply other threads:[~2015-04-30 12:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 12:14 [dpdk-dev] [PATCH v2 00/10] table: added table statistics Michal Jastrzebski
2015-04-30 12:14 ` Michal Jastrzebski [this message]
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 02/10] table: added acl table stats Michal Jastrzebski
2015-04-30 15:55 ` Stephen Hemminger
2015-05-18 10:57 ` Thomas Monjalon
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 03/10] table: added array " Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 04/10] table: added hash_ext " Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 05/10] table: added hash_key16 " Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 06/10] table: added hash_key32 " Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 07/10] table: added hash_key8 " Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 08/10] table: added hash_lru " Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 09/10] table: added lpm_ipv6 " Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 10/10] table: added lpm " Michal Jastrzebski
2015-05-05 15:10 ` [dpdk-dev] [PATCH v2 00/10] table: added table statistics Dumitrescu, Cristian
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=1430396078-968-2-git-send-email-michalx.k.jastrzebski@intel.com \
--to=michalx.k.jastrzebski@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).