From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <evgeny.agronsky@gmail.com>
Received: from mail-qk0-f177.google.com (mail-qk0-f177.google.com
 [209.85.220.177]) by dpdk.org (Postfix) with ESMTP id A7023DE0
 for <dev@dpdk.org>; Thu, 31 Aug 2017 09:35:51 +0200 (CEST)
Received: by mail-qk0-f177.google.com with SMTP id l65so37185716qkc.0
 for <dev@dpdk.org>; Thu, 31 Aug 2017 00:35:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=g2XvOMC5Hwb1l+2WFONAE9wf0WtcyRSv0NFpekiUCJI=;
 b=BDcXo8ngNmuaAnuQo54qwRlv7mBoYYmhuCxKDGjsF8lJ50h05wLAC/E5JyZ6pnTzup
 Qg6t9EfkHh+uNwWbu173VisManvHx5K2on18qaiCErfqZSVfAedmtRqowyGOr/wFq4Ej
 lRDG3VNAeWNwBD/hQ2EA4UyKd5MO38xL+LbpL15v/sFaQugV9oxyviNbH+uv23U3LWBN
 EUjBNI0CiQXp5Xf93wMW7ycBC4bCKRVALI4n4w3/015+si6sGE47m2JOK3nBrVuhPZwH
 0CdRJIH6h25kDP8eiZMIqtLPnoPUPwfPJD21LUwHzacELnhfzoU5CCpvYmFSboiiwiL7
 Xq8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=g2XvOMC5Hwb1l+2WFONAE9wf0WtcyRSv0NFpekiUCJI=;
 b=sz69TAFZ7IpKNWdH/OWddz/6UYuKIG8QSnFx/lmosg5I4AwH+uxcMo7yTWvtp1gvLu
 m7Gu19f24NF+99xgE4143iKIfSPcr6GCJQhQXW1nQ84POvrumGQlyy08rdb6aDSfcXOa
 YQfRcfsyreoUslSigeIv23wSi6fyyS3vsJGIu1T35bsTmyzRlvM9Z99ruS/1F6hJYC5J
 +gCYCuFkK9omveWLkjBCBm2yjEwD0ea7GRHshBnJ1g1XV0RRg0v/NtAjend8hr3eEqG9
 +/gBTpjbn6IzCjjVx9VH8J0hgYUB+u4BiXwlIS+EmO8sH0HgVbR3Ksp33RCjaFm/gj7s
 nhyw==
X-Gm-Message-State: AHYfb5iSfXIcHh8/WvVN+/BR8HXbvVT0rF386rzmxYx0WVU/N940HGV7
 uAI/7Zd4YGuSHV7Z/brTPASc3YSNJw==
X-Received: by 10.55.22.146 with SMTP id 18mr2219474qkw.112.1504164950881;
 Thu, 31 Aug 2017 00:35:50 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.105.6 with HTTP; Thu, 31 Aug 2017 00:35:50 -0700 (PDT)
From: Evgeny Agronsky <evgeny.agronsky@gmail.com>
Date: Thu, 31 Aug 2017 10:35:50 +0300
Message-ID: <CAKfnsPorMPS6Ls=tVm72vH6qE3g=RR5QCNXC=o21Pk_Vu3GhWQ@mail.gmail.com>
To: dev@dpdk.org
X-Mailman-Approved-At: Fri, 01 Sep 2017 17:10:44 +0200
Content-Type: text/plain; charset="UTF-8"
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] Why cuckoo based hashing in DPDK library?
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Aug 2017 07:35:51 -0000

Hello,

I'm using dpdk lib for various purposes, lately I needed to use a hashmap
for a certain needs and the one I found as part of the library was cuckoo
hashing based hashmap, I'm just wondering is there any reason for cuckoo
hashing? I'm basicly asking because of it's poor performance under high
table loads(and uses 2 hash funcs). Why not Hopscotch Hashing for example
which performs much better under loads, utilizes the cache and works well
with universal hash functions? I'm simply curious, maybe you have some sort
of benchmarks.

Thanks,
Evgeny Agronsky