News for hackers. Stuff that matters.
Re:HighwayHash: Strong hashing at 0.3 clock cycles per byte by jbapple on Saturday March 12, 2016 @08:41PM (#11275713)
> their proposed fix is more expensive than a HighwayTreeHash round.

For longish-strings, most of the cycles are in the preliminary rounds, so appending whatever you want onto the end should add negligible cost. This includes bitmixing (their proposed smhasher fix) or a HighwayTreeHash round.

Re:HighwayHash: Strong hashing at 0.3 clock cycles per byte by janwas on Tuesday March 15, 2016 @10:21AM (#11289788)
Agreed :) We (and SipHash developers) do care about short strings, though. Scripting language hash table inputs are typically around 10 bytes, so we can't ignore finalization overhead.