DPDK usage discussions
 help / color / mirror / Atom feed
From: Alex Kiselev <kiselev99@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "Fu, Qiaobin" <qiaobinf@bu.edu>, "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK hash table dynamic growth
Date: Mon, 17 Apr 2017 20:30:24 +0300	[thread overview]
Message-ID: <CAMKNYby-=xZHCs5LS4HCVRcZheu1bTyUCRh1aY=qb-JA5q62SA@mail.gmail.com> (raw)
In-Reply-To: <20170417095430.52cd5fdf@xeon-e3>

I would take a look at:

1) http://preshing.com/20160201/new-concurrent-hash-maps-for-cpp/
2) https://github.com/efficient/libcuckoo
3)
http://high-scale-lib.cvs.sourceforge.net/viewvc/high-scale-lib/high-scale-lib/org/cliffc/high_scale_lib/NonBlockingHashMap.java?view=markup
https://www.youtube.com/watch?v=HJ-719EGIts
https://www.youtube.com/watch?v=WYXgtXWejRM

But there is a catch, none of them is written in C.

2017-04-17 19:54 GMT+03:00 Stephen Hemminger <stephen@networkplumber.org>:
> On Mon, 17 Apr 2017 15:47:59 +0000
> "Fu, Qiaobin" <qiaobinf@bu.edu> wrote:
>
>> Hello,
>>
>> Currently, I am using the hash library to handle network flows defined as source and destination IP addresses. I need to find a way to alleviate memory pressure when the table is full. However, after some research, I didn’t find any hints on the dynamic growth in the hash library. Could anyone point me some hints on this? Thanks.
>>
>> Best,
>> Qiaobin
>
> If you need growing hash table, I recommend the lock-free hash table in the Linux userspace RCU library;
> rather than the more limited DPDK one.



-- 
--
Kiselev Alexander

  reply	other threads:[~2017-04-17 17:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-17 15:47 Fu, Qiaobin
2017-04-17 16:54 ` Stephen Hemminger
2017-04-17 17:30   ` Alex Kiselev [this message]
2017-04-17 17:44     ` Fu, Qiaobin
2017-04-17 20:06       ` Alex Kiselev
2017-04-18  5:08         ` Shyam Shrivastav

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='CAMKNYby-=xZHCs5LS4HCVRcZheu1bTyUCRh1aY=qb-JA5q62SA@mail.gmail.com' \
    --to=kiselev99@gmail.com \
    --cc=qiaobinf@bu.edu \
    --cc=stephen@networkplumber.org \
    --cc=users@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).