[cap-talk] FW: x.509 -- MD5 considered harmful today

[Bill Frantz]

zooko at zooko.com (zooko) on Wednesday, December 31, 2008 wrote:

>Commonly in this third category of uses the size of the data being  
>hashed can be large -- millions, billions or even trillions of bytes  
>at once -- and there is no public key operation or network delay to  
>hide the cost of the hash function. The hash function typically sits  
>squarely on the critical path of certain operations, and the speed of  
>the hash function is the limiting factor for the speed of those  
>operations.

In my experience, the code which performs the I/O is frequently expensive
enough to be a bottle neck. Many compression functions can pay for
themselves by reducing the CPU cost of the I/O. How do these hash functions
compare in CPU cost with common compression functions?

Cheers - Bill

-----------------------------------------------------------------------
Bill Frantz        | gets() remains as a monument | Periwinkle
(408)356-8506      | to C's continuing support of | 16345 Englewood Ave
www.pwpconsult.com | buffer overruns.             | Los Gatos, CA 95032