I was just thinking what you suggested as it would be costly
affair to kick accelerator for single block.
Well, single *or* small amount of blocks, with how small amount
depending on hardware overhead costs and software/hardware sustained
performance ratio. For example as per
http://
, September 10, 2008 3:47 AM
To: openssl-dev@openssl.org
Subject: Re: Hashing/MessageDigest in Engine
> And the answer I have
> is that the hashing normally is faster via soft lib than an
> engine/hardware.
Well, single block hashing is commonly faster in software, but hardware
should
> And the answer I have
> is that the hashing normally is faster via soft lib than an
> engine/hardware.
Well, single block hashing is commonly faster in software, but hardware
should beat it on multi-block operations. In other words one should aim
for "synergetic" implementation engaging hardware
Sitanshu,
To implement SHA1 in an ENGINE, create your own init/update/final functions and
put them in an EVP_MD structure.
write a function which returns the supported NIDs (e.g. NID_sha1), and then
call ENGINE_set_digests() before ENGINE_add().
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]