From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: "Jastrzebski, MichalX K" <michalx.k.jastrzebski@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 00/10] table: added table statistics
Date: Tue, 5 May 2015 15:10:20 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D891263235BB85@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <1430396078-968-1-git-send-email-michalx.k.jastrzebski@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Michal Jastrzebski
> Sent: Thursday, April 30, 2015 1:14 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v2 00/10] table: added table statistics
>
> From: Maciej Gajdzica <maciejx.t.gajdzica@intel.com>
>
> Added statistics for every type of table. By default all table statistics
> are disabled, user must activate them in config file.
>
> Maciej Gajdzica (10):
> table: added structure for storing table stats
> table: added acl table stats
> table: added array table stats
> table: added hash_ext table stats
> table: added hash_key16 table stats
> table: added hash_key32 table stats
> table: added hash_key8 table stats
> table: added hash_lru table stats
> table: added lpm_ipv6 table stats
> table: added lpm table stats
>
> config/common_bsdapp | 9 ++++++
> config/common_linuxapp | 9 ++++++
> lib/librte_table/rte_table.h | 25 +++++++++++++++
> lib/librte_table/rte_table_acl.c | 35 +++++++++++++++++++++
> lib/librte_table/rte_table_array.c | 34 +++++++++++++++++++-
> lib/librte_table/rte_table_hash_ext.c | 44
> ++++++++++++++++++++++++++
> lib/librte_table/rte_table_hash_key16.c | 41
> ++++++++++++++++++++++++
> lib/librte_table/rte_table_hash_key32.c | 41
> ++++++++++++++++++++++++
> lib/librte_table/rte_table_hash_key8.c | 52
> +++++++++++++++++++++++++++++++
> lib/librte_table/rte_table_hash_lru.c | 44
> ++++++++++++++++++++++++++
> lib/librte_table/rte_table_lpm.c | 34 ++++++++++++++++++++
> lib/librte_table/rte_table_lpm_ipv6.c | 34 ++++++++++++++++++++
> 12 files changed, 401 insertions(+), 1 deletion(-)
>
> --
> 1.7.9.5
Acked by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
prev parent reply other threads:[~2015-05-05 15:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 12:14 Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 01/10] table: added structure for storing table stats Michal Jastrzebski
2015-04-30 12:14 ` [dpdk-dev] [PATCH v2 02/10] table: added acl " 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 ` Dumitrescu, Cristian [this message]
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=3EB4FA525960D640B5BDFFD6A3D891263235BB85@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=michalx.k.jastrzebski@intel.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).