Re: [virtio-dev] Re: [PATCH v2 02/15] crypto: introduce crypto queue handler

[Ola Liljedahl <Ola.Liljedahl@arm.com>]

On 14/09/2016, 03:07, "Gonglei (Arei)" <arei.gonglei@huawei.com> wrote:

>Hi Ola,
>
>
>
>> -----Original Message-----
>> From: Ola Liljedahl [mailto:Ola.Liljedahl@arm.com]
>> Sent: Tuesday, September 13, 2016 7:53 PM
>> To: Paolo Bonzini; Daniel P. Berrange; Gonglei (Arei)
>> Cc: qemu-devel@nongnu.org; virtio-dev@lists.oasis-open.org; Huangpeng
>> (Peter); Luonengjun; mst@redhat.com; stefanha@redhat.com; Huangweidong
>> (C); mike.caraman@nxp.com; agraf@suse.de; xin.zeng@intel.com; Claudio
>> Fontana; nmorey@kalray.eu; vincent.jardin@6wind.com
>> Subject: Re: [virtio-dev] Re: [PATCH v2 02/15] crypto: introduce crypto
>>queue
>> handler
>>
>>
>>
>>
>>
>> On 13/09/2016, 12:58, "virtio-dev@lists.oasis-open.org on behalf of
>>Paolo
>> Bonzini" <virtio-dev@lists.oasis-open.org on behalf of
>> pbonzini@redhat.com> wrote:
>>
>> >
>> >
>> >On 13/09/2016 11:20, Daniel P. Berrange wrote:
>> >>> > +typedef struct CryptoPacket CryptoPacket;
>> >>> > +typedef struct CryptoQueue CryptoQueue;
>> >>> > +typedef struct CryptoPacketBuf CryptoPacketBuf;
>> >>> > +
>> >>> > +typedef void (CryptoPacketSent) (CryptoClientState *, int);
>> >> As previously, I'd expect naming of
>> >>
>> >>  QCryptoCryptodevPacket
>> >>  QCryptoCryptodevPacketBuf
>> >>  QCryptoCryptodevQueue
>> >>
>> >
>> >Gonglei,
>> >
>> >you are copying a lot of code from network backends.
>> >
>> >I am not sure why you would need a queue for virtio-crypto rather than
>>a
>> >direct connection between frontend and backend (and the backend would
>>be
>> >QEMU crypto APIs, like Daniel suggested).
>>
>> What about backends implemented directly in HW? Bypass the middle man.
>> Make crypto offload meaningful for small size blocks.
>>
>As I said in other reply, I only provide interfaces, you can realize them
>according
>to different backend cryptodevs.
Interfaces imposes contraints on performance and implementation. A poor
interface could make certain implementations unnecessarily difficult.
Since these virtio-* interfaces will live for a long time, we should
ensure that they do not impose unnecessary constraints. For functionality
like crypto and IPsec, I can see the benefit of implementing the backend
in HW (for the datapath).

>
>Regards,
>-Gonglei
>
>> < Ola
>>
>> >
>> >Paolo
>> >
>> >---------------------------------------------------------------------
>> >To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
>> >For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
>> >
>>
>> IMPORTANT NOTICE: The contents of this email and any attachments are
>> confidential and may also be privileged. If you are not the intended
>>recipient,
>> please notify the sender immediately and do not disclose the contents
>>to any
>> other person, use it for any purpose, or store or copy the information
>>in any
>> medium. Thank you.
>

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.