From: "Mcnamara, John" <john.mcnamara@intel.com>
To: Andriy Berestovskyy <aber@semihalf.com>,
Evgeny Agronsky <evgeny.agronsky@gmail.com>
Cc: DPDK <dev@dpdk.org>
Subject: Re: [dpdk-dev] Why cuckoo based hashing in DPDK library?
Date: Wed, 13 Sep 2017 16:49:12 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE23EDA7108@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <CAOysbxpQXCb2Fy6_p0-JZrxbB8pd=-N=A6LeLt4-5BQQrBvqSQ@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Andriy Berestovskyy
> Sent: Friday, September 1, 2017 5:15 PM
> To: Evgeny Agronsky <evgeny.agronsky@gmail.com>
> Cc: DPDK <dev@dpdk.org>
> Subject: Re: [dpdk-dev] Why cuckoo based hashing in DPDK library?
>
> Hey Evgeny,
> Please see inline.
>
> On Thu, Aug 31, 2017 at 9:35 AM, Evgeny Agronsky
> <evgeny.agronsky@gmail.com> wrote:
> > I'm basicly asking because of it's poor performance under high
>
> Well, it is not the academic cuckoo hash implementation, so the
> performance is not that bad and it also utilizes cache ;)
>
> Please have a look at this paper for more details:
> http://www.cs.cmu.edu/~dongz/papers/cuckooswitch.pdf
>
> > with universal hash functions? I'm simply curious, maybe you have some
> > sort of benchmarks.
>
> Once someone implement a Hopscotch for DPDK, we could run some
> benchmarks... ;) But sure, it would be great to have a faster hash
> implementation, since DPDK is all about performance...
Hi,
It might be worth having a generic hash interface in DPDK that other hash algorithms could be inserted under so that comparisons/replacements would be easier.
John
next prev parent reply other threads:[~2017-09-13 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 16:15 Andriy Berestovskyy
2017-09-13 16:49 ` Mcnamara, John [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-08-31 7:35 Evgeny Agronsky
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=B27915DBBA3421428155699D51E4CFE23EDA7108@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=aber@semihalf.com \
--cc=dev@dpdk.org \
--cc=evgeny.agronsky@gmail.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).