On 09/24/2012 08:46 PM, Lluís Batlle i Rossell wrote:
>> There will be no much change. If you mv_cesa doesn't support sha1, it >> may be faster to use the userspace implementation of sha1. > I got it working. Simply, the mv_cesa wants a 'fallback'. Maybe for some > shorter-than-usual-length blocks or so. No idea. > 'openssl speed' shows a big improvement on sha1. Nevertheless, on openssh I > don't see much improvement (aes128+sha1), although both are used through > cryptodev. With 'perf top', I see that all the time is spent in memcpy, both > at > the kernel mv_crypto thread and the userspace sshd. No idea how to get a > faster > scp/sftp. memcpy? Do you see any error message "Error getting user pages. Falling back to non zero copy." to kernel log? The cryptodev operation is pretty much zero copy otherwise (unless you do the crypt_op operation and specify the flag COP_FLAG_NO_ZC). regards, Nikos _______________________________________________ Cryptodev-linux-devel mailing list Cryptodev-linux-devel@gna.org https://mail.gna.org/listinfo/cryptodev-linux-devel
