search for: _verify_

I think you're missing a point here. Two different checksum algorithms are used in concert, the Adler-based one and the MD5 one. I SSE-optimized the Adler-based one. The Adler-based hash is used to _find_ blocks that might have shifted, while the MD5 hash is a strong cryptographic hash used to _verify_ blocks and files. You wouldn't want to replace the MD5 hash with the Adler-based hash, they are of a different class. If you'd replace the MD5 hash with a different one, you'd replace it with one of the SHA's or even xxHash. On Mon, May 18, 2020 at 6:21 PM Ben RUBSON via rsync <...

Hi! I noticed when upgrading asterisk that the latest version of asterisk is not recognizing the version of asterisk-addons properly. When you clean out /usr/lib/asterisk/modules and then install zaptel-1.2.12 -> libpri-1.2.4 -> asterisk 1.2.14 -> asterisk-addons-1.2.5 and then you compile and install asterisk *again* it complains that the modules of asterisk-addons are not built

Well, don't get too excited, get_checksum1() (the function optimized here) is not the great performance limiter in this case, it's get_checksum2() and sum_update(), which will be using MD5. You can force using MD4, but on the slower CPU's I've tested in practice that is slower rather than faster, contrary to what would be expected. While this patch will improve things a little, to