Hello, I have written sha and aes HW accelerator drivers for our custom drivers (thanks for your patient help) and they work great. To exploit the full potential of the HW I want to port them to the ASYNC interface and have some questions. 1. Using my current setup I see the following results (measured with iperf) no ipsec -85 mbits ESP in tunnel mode with null algs - 45 mbits ESP in tunnel mode with aes and sha1 - 32 mbits Is it reasonable to have the throughput drop so much even without any actual crypto going on? Can this mostly be attributed to the bigger packets ? My understanding of the results is that the maximum throughput I can hope to achieve on this systen by only improving the crypto drivers is 45 mbits? 2. Is there any comparison somewhere between OCF performance and Acrypto? 3. Using drivers/crypto/talitos as a reference I am setting the alg name to "authenc(hmac(sha1),cbc(aes))",cra_flags to CRYPTO_ALG_TYPE_AEAD | CRYPTO_ALG_ASYNC; and cra_type to &crypto_aead_type. My existing driver had a cra_list field. Is that required for this type of driver as well? Thanks, Avital -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
