From: "Edupuganti, Saikrishna" <saikrishna.edupuganti@intel.com>
To: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>
Subject: Re: [dpdk-dev] [PATCH 0/3] Hash library fixes
Date: Tue, 27 Sep 2016 22:34:18 +0000 [thread overview]
Message-ID: <BA6ACE951634D6448765516F703B1C3019B67560@ORSMSX116.amr.corp.intel.com> (raw)
In-Reply-To: <1472247009-166860-1-git-send-email-pablo.de.lara.guarch@intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pablo de Lara
> Sent: Friday, August 26, 2016 2:30 PM
> To: dev@dpdk.org
> Cc: Richardson, Bruce <bruce.richardson@intel.com>; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> Subject: [dpdk-dev] [PATCH 0/3] Hash library fixes
>
> This patchset includes some minor fixes to the hash library, plus a small
> improvement in checking for an empty slot when performing different hash
> operations.
>
> Pablo de Lara (3):
> hash: fix ring size
> hash: fix false zero signature key hit lookup
> hash: check if slot is empty with key index
>
> lib/librte_hash/rte_cuckoo_hash.c | 24 +++++++++++++++---------
> lib/librte_hash/rte_cuckoo_hash.h | 2 ++
> lib/librte_hash/rte_cuckoo_hash_x86.h | 5 ++---
> 3 files changed, 19 insertions(+), 12 deletions(-)
>
> --
> 2.7.4
Series-acked-by: Saikrishna Edupuganti <saikrishna.edupuganti@intel.com>
next prev parent reply other threads:[~2016-09-27 22:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 21:30 Pablo de Lara
2016-08-26 21:30 ` [dpdk-dev] [PATCH 1/3] hash: fix ring size Pablo de Lara
2016-08-26 21:30 ` [dpdk-dev] [PATCH 2/3] hash: fix false zero signature key hit lookup Pablo de Lara
2016-08-26 21:30 ` [dpdk-dev] [PATCH 3/3] hash: check if slot is empty with key index Pablo de Lara
2016-08-29 6:58 ` [dpdk-dev] [PATCH 0/3] Hash library fixes Christian Ehrhardt
2016-09-27 22:34 ` Edupuganti, Saikrishna [this message]
2016-09-29 19:52 ` 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=BA6ACE951634D6448765516F703B1C3019B67560@ORSMSX116.amr.corp.intel.com \
--to=saikrishna.edupuganti@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=pablo.de.lara.guarch@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).