From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] Fwd: curious about hashing comments on cake
Date: Fri, 8 Jan 2016 12:58:51 -0800 [thread overview]
Message-ID: <CAA93jw5Zmmu7E8hfu4vCTR_ma=e8ynEbuJmaTsuz0Z=+V7anKA@mail.gmail.com> (raw)
In-Reply-To: <CAJts4a2fW-j3hw-gKhshrJ9O115jf_gWqsdOAb=XikVgqiXGUw@mail.gmail.com>
---------- Forwarded message ----------
From: Dave Acker <soldack@gmail.com>
Date: Fri, Jan 8, 2016 at 12:48 PM
Subject: curious about hashing comments on cake
To: dave.taht@gmail.com
On http://www.bufferbloat.net/projects/codel/wiki/CakeTechnical, it
says that the hash used by fq_codel had various issues and that "we
have also found that the hash function fq_codel relies on is
suboptimal." I believe that fq_codel uses the Jenkins hash like many
other parts of linux. What was suboptimal about it? The page notes
the birthday problem but was there anything else?
-Dave Acker
next parent reply other threads:[~2016-01-08 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJts4a2fW-j3hw-gKhshrJ9O115jf_gWqsdOAb=XikVgqiXGUw@mail.gmail.com>
2016-01-08 20:58 ` Dave Taht [this message]
2016-01-08 21:15 ` Jonathan Morton
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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw5Zmmu7E8hfu4vCTR_ma=e8ynEbuJmaTsuz0Z=+V7anKA@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@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