From: David Miller <davem@davemloft.net>
To: kadlec@blackhole.kfki.hu
Cc: netdev@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] Update jhash.h with the new version of Jenkins' hash
Date: Tue, 10 Feb 2009 17:17:38 -0800 (PST) [thread overview]
Message-ID: <20090210.171738.65421666.davem@davemloft.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0902102026060.10299@blackhole.kfki.hu>
From: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Date: Tue, 10 Feb 2009 20:40:47 +0100 (CET)
> Please consider applying the following patch:
>
> The current jhash.h implements the lookup2() hash function by Bob Jenkins.
> However, lookup2() is outdated as Bob wrote a new hash function called
> lookup3(). The new hash function
>
> - mixes better than lookup2(): it passes the check that every input bit
> changes every output bit 50% of the time, while lookup2() failed it.
> - performs better: compiled with -O2 on Core2 Duo, lookup3() 20-40% faster
> than lookup2() depending on the key length.
>
> The patch replaces the lookup2() implementation of the 'jhash*'
> functions with that of lookup3().
>
> You can read a longer comparison of the two and other hash functions at
> http://burtleburtle.net/bob/hash/doobs.html.
>
> Signed-off-by: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
I support this change and I also don't think it makes sense
to have a jhash3.h new header file, that's just a waste of
time. Either the new stuff is better or it isn't, and that
whole "matching hashes" argument is pure garbage.
But this kind of change isn't for me to decide, changing jhash
impacts the entire tree not just networking, and also I know
that Rusty Russell was investigating making this change and
he even did his own timings on various platforms.
Therefore this needs to be proposed on linux-kernel with appropriate
parties CC:'d.
Thanks.
next prev parent reply other threads:[~2009-02-11 1:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 19:40 [PATCH] Update jhash.h with the new version of Jenkins' hash Jozsef Kadlecsik
2009-02-10 21:19 ` Scott Feldman
2009-02-10 22:03 ` Jozsef Kadlecsik
2009-02-11 1:17 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-11 10:19 Jozsef Kadlecsik
2009-02-11 20:19 ` Michał Mirosław
2009-02-11 22:50 ` Jozsef Kadlecsik
2009-02-11 23:23 ` Michał Mirosław
2009-02-12 0:12 ` wli
2009-02-12 0:29 ` David Miller
2009-02-12 0:41 ` Jan Engelhardt
2009-02-12 9:05 ` Jarek Poplawski
2009-02-12 9:55 ` Jarek Poplawski
2009-02-12 9:11 ` Jozsef Kadlecsik
2009-02-12 9:16 ` Patrick McHardy
2009-02-12 9:41 ` Jozsef Kadlecsik
2009-02-12 13:46 ` Kyle Moffett
2009-02-17 17:13 ` Jozsef Kadlecsik
2009-02-18 5:11 ` Rusty Russell
2009-02-18 11:50 ` Ilpo Järvinen
2009-02-12 19:58 ` Eric W. Biederman
2009-02-12 2:58 ` Rusty Russell
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=20090210.171738.65421666.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.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).