On Tue, Apr 30, 2013 at 6:51 AM, Anthony Foiani <anthony.foi...@gmail.com> wrote:
> SHA1 -- about 2.5x slower using cryptodev than native CPU > instructions. Is that expected? In some (many?) systems the CPU can handle hashes much faster than the crypto chip. Note also that in that time includes the context switch from user-space to kernel space. It depends on you on whether you want to off-load that operation from the CPU, and do something else with it. If your system is generally idle you could avoid cryptodev for hashes. > RSA -- signing seems to be exactly the same, while verifying is about > 10% faster in native. That seems odd, since cryptodev advertises RSA > capabilities, and the SEC v3.3 engine of the MPC8315E supports RSA > operations. cryptodev-linux does not support modular exponentiation with cryptodev because the Linux kernel crypto drivers don't include that capability. So you shouldn't see any difference with RSA. > Finally, why does specifying the EVP result in such a huge difference? > E.g, with aes-128-cbc and 8KiB blocks: > no cryptodev, no evp -- 6MiB/s > no cryptodev, with evp -- 6MiB/s > with cryptodev, no evp -- 6MiB/s No evp in openssl means that the software implementation is used (not the cryptodev engine). > with cryptodev, with evp -- 33MiB/s (!) Here the engine is used. regards, Nikos _______________________________________________ Cryptodev-linux-devel mailing list Cryptodev-linux-devel@gna.org https://mail.gna.org/listinfo/cryptodev-linux-devel
