[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v8 1/1] crypto: add virtio-crypto driver

From: Christian Borntraeger
Subject: Re: [Qemu-devel] [PATCH v8 1/1] crypto: add virtio-crypto driver
Date: Tue, 10 Jan 2017 13:27:04 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1

On 12/15/2016 03:03 AM, Gonglei wrote:
> +
> +static struct crypto_alg virtio_crypto_algs[] = { {
> +     .cra_name = "cbc(aes)",
> +     .cra_driver_name = "virtio_crypto_aes_cbc",
> +     .cra_priority = 501,

This is still higher than the hardware-accelerators (like intel aesni or the
s390 cpacf functions or the arm hw). aesni and s390/cpacf are supported by the
hardware virtualization and available to the guests. I do not see a way how 
crypto can be faster than that (in the end it might be cpacf/aesni + overhead)
instead it will very likely be slower.
So we should use a number that is higher than software implementations but
lower than the hw ones.

Just grepping around, the software ones seem be be around 100 and the hardware 
ones around 200-400. So why was 150 not enough?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]