Meow 0.6 candidate functions about meow_hash HOT 4 OPEN

Awesome! I will take a look.

Separately, I am curious: the four-parallel-track construction is how I did the original Meow Hash (the one that didn't have enough diffusion). I am curious: if it can work for AVX-512, why was it not able to be retained from the original Meow Hash for 128-bit? Because in general, parallel-stream construction is the best kind of construction for throughput, since AES instructions have 4-cycle latency...

- Casey

from meow_hash.

I didn't think of this until now, maybe you considered this construction obvious, but I just thought that if we did parallel tracks we would run out of registers, and thus add a bunch of overhead to the 128 bit implementation.

from meow_hash.

Well, it's not so much that I considered it obvious as that it was the original design of Meow Hash :) My assumption was that since you didn't use any parallel construction in your blocks for the 128-bit version, your reasoning was that the hash was not as good if it was mixed at the end. But I guess that is not true? If not, that is excellent, because the more parallel tracks you can do, the faster you can go, typically, and that's why I designed the original one that way.

• Casey

from meow_hash.

So, since I was looking at Chacha20 and AES-256-ctr recently, I also have some important updates: it turns out both Zen2/3 and Tiger Lake added a second AES unit. That means that parallel construction becomes much more important now for speed, because the newer x64 chips can issue two AES instructions every cycle even without VAES!

I need to take a look at what you've got so far @NoHatCoder and I'll think about how it will arrange.

- Casey

from meow_hash.