There's a "drivers/crypto/padlock-sha.c" driver implementation in the standard kernel.
How does the openssl speed benchmark compare to bitcoin's khash/s?
On my Core2Duo E8500, it's:
How does the openssl speed benchmark compare to bitcoin's khash/s?
Code:
openssl speed -evp sha256
On my Core2Duo E8500, it's:
Code:
The 'numbers' are in 1000s of bytes per second processed.
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha256 25568.41k 60726.70k 108968.11k 137848.27k 146604.46k
type 16 bytes 64 bytes 256 bytes 1024 bytes 8192 bytes
sha256 25568.41k 60726.70k 108968.11k 137848.27k 146604.46k
That's a good question. I'm not on my home machine right now so I can't compare khash/s to the OpenSSL benchmark. On the largest block size in that benchmark, it looks like your machine does about 1.2 Gbit/sec (146604.46 * 1000 *
. So if the VIA chip can reach its full potential it would be about 4 times as fast.I assumed that since bitcoin appears to be built on OpenSSL you would just need to rebuild it from source on your VIA machine with Padlock-aware OpenSSL, but maybe there is more to it.
I think the most common VIA use right now is in netbooks. I would be pretty amused if a little $350 netbook with this processor could keep up with an i5 or Phenom II. I bet a good CUDA hasher can thrash it, but I wouldn't be surprised if the VIA chip wins on hashes per dollar of hardware and per dollar of electricity.