From: Dave Taht <dave.taht@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>, codel@lists.bufferbloat.net
Subject: Re: [Codel] found another good use for a queue today, possibly
Date: Thu, 29 Nov 2018 09:17:41 -0800 [thread overview]
Message-ID: <CAA93jw6-6sfUXgAvTcKnTPdpnKAyG4ishNC4f_ycD-_bvR58aA@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw6HBms4JMBgH1kSNLCiR2uvGzNBtzL920Cr=RqzGZ2-BQ@mail.gmail.com>
His thesis is more clear:
https://sites.google.com/site/yuriyarbitman/Home/de-amortizedcuckoohashing
He did exclude the cost of a resize, but, still... I find the core
idea very attractive.
We swapped an email and he said:
> In general, I would say that a cryptographic hash function will do.
> If you want to use a non-cryptographic hash function, then the
> question is what provable random properties it has. This is also
> discussed in the thesis and in the paper.
On Mon, Nov 26, 2018 at 6:17 PM Dave Taht <dave.taht@gmail.com> wrote:
>
> I had been investigating various hashing schemes for speeding up the
> babeld routing protocol daemon, and dealing with annoying bursty cpu
> behavior (resizing memory, bursts of packets, thundering herds of
> retractions), and, although it's a tough slog of a read, this adds a
> queue to cuckoo hashing to good effect in flattening out insertion
> time.
>
> https://arxiv.org/pdf/0903.0391.pdf
>
> But for all I know it's dependent on angels dancing on saddles mounted
> on unicorns. I skip to the graphs for insertion time and go back to
> the text for another round...
>
> "polylog(n)-wise Independent Hash Function". OK, my google-foo fails
> me: The authors use sha1, would something lighter weight suit?
>
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
prev parent reply other threads:[~2018-11-29 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 2:17 Dave Taht
2018-11-27 4:08 ` Stephen Hemminger
2018-11-27 4:17 ` [Codel] [Bloat] " Jonathan Morton
2018-11-29 4:37 ` Dave Taht
2018-11-29 17:17 ` Dave Taht [this message]
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
List information: https://lists.bufferbloat.net/postorius/lists/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6-6sfUXgAvTcKnTPdpnKAyG4ishNC4f_ycD-_bvR58aA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=codel@lists.bufferbloat.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