From: roy.fan.zhang@intel.com
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v4 0/7] librte_table: add key_mask parameter to
Date: Wed, 28 Oct 2015 17:11:15 +0000 [thread overview]
Message-ID: <1446052282-22391-1-git-send-email-roy.fan.zhang@intel.com> (raw)
From: Fan Zhang <roy.fan.zhang@intel.com>
This patchset links to ABI change announced for librte_table.
The key_mask parameters has been added to the hash table
parameter structure for 8-byte key and 16-byte key extendible
bucket and LRU tables.
v2:
*updated release note
v3:
*merged release note with source code patch
*fixed build error: added missing symbol to
librte_table/rte_table_version.map
v4:
*modified rte_prefetch offsets to improve hash/lru table
lookup performance.
Acked-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Fan Zhang (7):
librte_table: add key_mask parameter to 8- and 16-bytes key hash
parameters
librte_table: add 16 byte hash table operations with computed lookup
app/test: modify app/test_table_combined and app/test_table_tables
app/test-pipeline: modify pipeline test
example/ip_pipeline: add parse_hex_string for internal use
example/ip_pipeline/pipeline: update flow_classification pipeline
librte_table: performance improvement on rte_prefetch offset
app/test-pipeline/pipeline_hash.c | 4 +
app/test/test_table_combined.c | 5 +-
app/test/test_table_tables.c | 6 +-
doc/guides/rel_notes/deprecation.rst | 4 -
doc/guides/rel_notes/release_2_2.rst | 4 +
examples/ip_pipeline/config_parse.c | 52 +++
.../pipeline/pipeline_flow_classification_be.c | 56 ++-
examples/ip_pipeline/pipeline_be.h | 4 +
lib/librte_table/rte_table_hash.h | 20 +
lib/librte_table/rte_table_hash_ext.c | 10 +-
lib/librte_table/rte_table_hash_key16.c | 446 +++++++++++++++++++--
lib/librte_table/rte_table_hash_key32.c | 35 +-
lib/librte_table/rte_table_hash_key8.c | 105 +++--
lib/librte_table/rte_table_hash_lru.c | 10 +-
lib/librte_table/rte_table_version.map | 7 +
15 files changed, 673 insertions(+), 95 deletions(-)
--
2.1.0
next reply other threads:[~2015-10-28 17:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 17:11 roy.fan.zhang [this message]
2015-10-28 17:11 ` [dpdk-dev] [PATCH v4 1/7] librte_table: add key_mask parameter to 8- and 16-bytes key hash parameters roy.fan.zhang
2015-10-28 17:11 ` [dpdk-dev] [PATCH v4 2/7] librte_table: add 16 byte hash table operations with computed lookup roy.fan.zhang
2015-10-28 17:11 ` [dpdk-dev] [PATCH v4 3/7] app/test: modify app/test_table_combined and app/test_table_tables roy.fan.zhang
2015-10-28 17:11 ` [dpdk-dev] [PATCH v4 4/7] app/test-pipeline: modify pipeline test roy.fan.zhang
2015-10-28 17:11 ` [dpdk-dev] [PATCH v4 5/7] example/ip_pipeline: add parse_hex_string for internal use roy.fan.zhang
2015-10-28 17:11 ` [dpdk-dev] [PATCH v4 6/7] example/ip_pipeline/pipeline: update flow_classification pipeline roy.fan.zhang
2015-10-28 17:11 ` [dpdk-dev] [PATCH v4 7/7] librte_table: performance improvement on rte_prefetch offset roy.fan.zhang
2015-11-25 22:33 ` [dpdk-dev] [PATCH v4 0/7] librte_table: add key_mask parameter to 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=1446052282-22391-1-git-send-email-roy.fan.zhang@intel.com \
--to=roy.fan.zhang@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).