From: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org
Subject: [dpdk-dev] [pull-request] next-pipeline 18.05 pre-rc3
Date: Tue, 8 May 2018 17:54:44 +0100 [thread overview]
Message-ID: <1525798484-163383-1-git-send-email-cristian.dumitrescu@intel.com> (raw)
The following changes since commit e2077a158e22451144d1b023f949f3232cfa62b3:
doc: add DPAA2 QDMA rawdev guide (2018-05-08 12:21:13 +0200)
are available in the git repository at:
http://dpdk.org/git/next/dpdk-next-pipeline
for you to fetch changes up to 93428c4929c97f9cd7b8cbf449070a2924501557:
table: add dedicated params struct for cuckoo hash (2018-05-08 15:19:58 +0100)
----------------------------------------------------------------
Fan Zhang (4):
examples/ip_pipeline: fix uninitialized scalar variable
examples/ip_pipeline: fix logically dead node
examples/ip_pipeline: fix buffer not null terminated.
examples/ip_pipeline: fix buffer not null terminated
Jasvinder Singh (5):
examples/ip_pipeline: fix memory leak
examples/ip_pipeline: fix buffer not null terminated
examples/ip_pipeline: fix buffer not null terminated
examples/ip_pipeline: fix buffer not null terminated
table: add dedicated params struct for cuckoo hash
Kevin Laatz (3):
examples/ip_pipeline: fix resource leak
examples/ip_pipeline: fix buffer not null terminated
examples/ip_pipeline: fix buffer not null terminated
Reshma Pattan (4):
examples/ip_pipipeline: fix resource leak
examples/ip_pipeline: fixes uninitialized scalar variable
examples/ip_pipeline: fix buffer not null terminated
examples/ip_pipeline: fix buffer not null terminated
examples/ip_pipeline/action.c | 6 ++--
examples/ip_pipeline/cli.c | 12 +++----
examples/ip_pipeline/conn.c | 3 ++
examples/ip_pipeline/kni.c | 3 +-
examples/ip_pipeline/link.c | 3 +-
examples/ip_pipeline/mempool.c | 3 +-
examples/ip_pipeline/pipeline.c | 3 +-
examples/ip_pipeline/swq.c | 4 ++-
examples/ip_pipeline/tap.c | 13 +++++---
examples/ip_pipeline/tmgr.c | 4 ++-
lib/librte_table/Makefile | 1 +
lib/librte_table/meson.build | 1 +
lib/librte_table/rte_table_hash.h | 3 --
lib/librte_table/rte_table_hash_cuckoo.c | 11 +++---
lib/librte_table/rte_table_hash_cuckoo.h | 57 ++++++++++++++++++++++++++++++++
test/test-pipeline/main.h | 4 +++
test/test-pipeline/pipeline_hash.c | 26 ++++++++++++++-
test/test/test_table.c | 11 ++++++
test/test/test_table.h | 6 ++++
test/test/test_table_combined.c | 4 +--
test/test/test_table_tables.c | 6 ++--
21 files changed, 151 insertions(+), 33 deletions(-)
create mode 100644 lib/librte_table/rte_table_hash_cuckoo.h
next reply other threads:[~2018-05-08 16:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 16:54 Cristian Dumitrescu [this message]
2018-05-10 1:29 ` 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=1525798484-163383-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).