From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-pipeline 17.11 pre-rc2
Date: Wed, 18 Oct 2017 18:10:57 +0100 [thread overview]
Message-ID: <1508346657-58095-1-git-send-email-cristian.dumitrescu@intel.com> (raw)
The following changes since commit 6b9ed026a8704b9e5ee5da7997617ef7cc82e114:
igb_uio: fix build with kernel <= 3.17 (2017-10-16 13:07:11 +0200)
are available in the git repository at:
http://dpdk.org/git/next/dpdk-next-pipeline
for you to fetch changes up to 32ba3d320664a84bbd4575af3d85b78721cd6d34:
doc: remove deprecation notice for librte_table (2017-10-18 17:57:06 +0100)
----------------------------------------------------------------
Cristian Dumitrescu (18):
test: removing calls to deprecated hash tables
librte_table: remove deprecated 8-byte key hash tables
librte_table: remove deprecated 16-byte key hash tables
librte_table: remove deprecated variable size key ext hash tables
librte_table: remove deprecated variable size key lru hash tables
librte_table: rename cuckoo hash table ops
librte_table: add unified params structure and mask-based hash func
librte_table: rework variable size key ext hash tables
librte_table: rework variable size key lru hash table
librte_table: rework 8-byte key hash tables
librte_table: rework 16-byte key hash tables
librte_table: rework 32-byte key hash tables
librte_table: rework cuckoo hash table
test: add mask-based hash functions
librte_table: cosmetic enhancements in api file
librte_table: copyright cosmetic updates
librte_table: map file updates
doc: remove deprecation notice for librte_table
doc/guides/rel_notes/deprecation.rst | 6 -
examples/ip_pipeline/pipeline/hash_func.h | 176 +++--
.../pipeline/pipeline_flow_classification.c | 10 +-
.../pipeline/pipeline_flow_classification_be.c | 51 +-
.../ip_pipeline/pipeline/pipeline_passthrough_be.c | 10 +-
.../ip_pipeline/pipeline/pipeline_routing_be.c | 14 +-
lib/librte_table/rte_table_hash.h | 305 +--------
lib/librte_table/rte_table_hash_cuckoo.c | 205 +++---
lib/librte_table/rte_table_hash_ext.c | 417 ++++--------
lib/librte_table/rte_table_hash_key16.c | 750 ++++++---------------
lib/librte_table/rte_table_hash_key32.c | 436 +++++++-----
lib/librte_table/rte_table_hash_key8.c | 716 ++++++--------------
lib/librte_table/rte_table_hash_lru.c | 513 ++++++--------
lib/librte_table/rte_table_version.map | 23 +-
test/test-pipeline/main.h | 5 +-
test/test-pipeline/pipeline_hash.c | 107 +--
test/test/test_table.c | 1 +
test/test/test_table.h | 3 +-
test/test/test_table_combined.c | 137 ++--
test/test/test_table_tables.c | 150 ++---
20 files changed, 1440 insertions(+), 2595 deletions(-)
next reply other threads:[~2017-10-18 17:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-18 17:10 Cristian Dumitrescu [this message]
2017-10-24 14:48 ` 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=1508346657-58095-1-git-send-email-cristian.dumitrescu@intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).