From: Sankar Chokkalingam <sankarx.chokkalingam@intel.com>
To: dev@dpdk.org
Cc: cristian.dumitrescu@intel.com, jasvinder.singh@intel.com,
sankarx.chokkalingam@intel.com,
Guruprasad Rao <guruprasadx.rao@intel.com>
Subject: [dpdk-dev] [PATCH 0/3] changes for enabling cuckoo hash into table library
Date: Thu, 22 Sep 2016 03:12:04 -0700 [thread overview]
Message-ID: <1474539127-232221-1-git-send-email-sankarx.chokkalingam@intel.com> (raw)
From: Guruprasad Rao <guruprasadx.rao@intel.com>
Guruprasad Rao (3):
lib/librte_table: enabling cuckoo hash into table library
app/test-pipeline: added cuckoo hash for benchmarking
app/test: adding cuckoo hash table for testing
app/test-pipeline/config.c | 20 +-
app/test-pipeline/main.c | 12 +-
app/test-pipeline/main.h | 12 +-
app/test-pipeline/pipeline_hash.c | 59 +++++
app/test/test_table_combined.c | 72 +++++-
app/test/test_table_combined.h | 3 +-
app/test/test_table_tables.c | 167 +++++++++++++-
app/test/test_table_tables.h | 3 +-
lib/librte_table/Makefile | 4 +-
lib/librte_table/rte_table_hash.h | 31 ++-
lib/librte_table/rte_table_hash_cuckoo.c | 382 +++++++++++++++++++++++++++++++
lib/librte_table/rte_table_version.map | 7 +
12 files changed, 763 insertions(+), 9 deletions(-)
create mode 100644 lib/librte_table/rte_table_hash_cuckoo.c
--
2.5.0
next reply other threads:[~2016-09-22 10:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 10:12 Sankar Chokkalingam [this message]
2016-09-22 10:12 ` [dpdk-dev] [PATCH 1/3] lib/librte_table: " Sankar Chokkalingam
2016-09-22 10:12 ` [dpdk-dev] [PATCH 2/3] app/test-pipeline: added cuckoo hash for benchmarking Sankar Chokkalingam
2016-09-22 10:12 ` [dpdk-dev] [PATCH 3/3] app/test: adding cuckoo hash table for testing Sankar Chokkalingam
2016-09-23 12:54 ` [dpdk-dev] [PATCH 0/3] changes for enabling cuckoo hash into table library Dumitrescu, Cristian
2016-10-12 20:11 ` 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=1474539127-232221-1-git-send-email-sankarx.chokkalingam@intel.com \
--to=sankarx.chokkalingam@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=guruprasadx.rao@intel.com \
--cc=jasvinder.singh@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).