qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Gonglei (Arei)" <arei.gonglei@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "mst@redhat.com" <mst@redhat.com>,
	"Huangweidong (C)" <weidong.huang@huawei.com>,
	"stefanha@redhat.com" <stefanha@redhat.com>,
	"Zhoujian (jay)" <jianjay.zhou@huawei.com>,
	"pasic@linux.vnet.ibm.com" <pasic@linux.vnet.ibm.com>,
	longpeng <longpeng2@huawei.com>,
	"xin.zeng@intel.com" <xin.zeng@intel.com>,
	"roy.fan.zhang@intel.com" <roy.fan.zhang@intel.com>
Subject: Re: [Qemu-devel] [PATCH 3/4] cryptodev-vhost-user: add crypto session handler
Date: Tue, 28 Nov 2017 11:45:31 +0100	[thread overview]
Message-ID: <b98e2b09-35e7-47c2-b49f-982a09804b4f@redhat.com> (raw)
In-Reply-To: <33183CC9F5247A488A2544077AF19020DA4A7DC2@DGGEMA505-MBS.china.huawei.com>

On 28/11/2017 11:43, Gonglei (Arei) wrote:
>> As far as I understand, VIRTIO_CRYPTO_CIPHER_CREATE_SESSION is called as
>> a result of sending a message on the control virtqueue.
>
> VIRTIO_CRYPTO_CIPHER_CREATE_SESSION is a message type of control queue,
> Means creating a session for next crypto requests.

Ok, so the message does have the same meaning as the control queue
message.  Thanks for confirming.

>> Why can't vhost-user also process create/destroy session messages on the
>> control virtqueue, instead of having device-specific messages in the
>> protocol?
>
> You mean we can share control virtqueue to DPDK as well? Like data queues?

I don't know :) but why not?

Thanks,

Paolo

  reply	other threads:[~2017-11-28 10:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  9:03 [Qemu-devel] [PATCH 0/4] cryptodev: add vhost support Gonglei
2017-11-28  9:03 ` [Qemu-devel] [PATCH 1/4] cryptodev: add vhost-user as a new cryptodev backend Gonglei
2017-11-28  9:03 ` [Qemu-devel] [PATCH 2/4] cryptodev: add vhost support Gonglei
2017-11-28  9:03 ` [Qemu-devel] [PATCH 3/4] cryptodev-vhost-user: add crypto session handler Gonglei
2017-11-28 10:01   ` Paolo Bonzini
2017-11-28 10:43     ` Gonglei (Arei)
2017-11-28 10:45       ` Paolo Bonzini [this message]
2017-11-28 11:06         ` Gonglei (Arei)
2017-11-28 11:19           ` Paolo Bonzini
2017-11-29  2:33             ` Gonglei (Arei)
2017-11-29  4:10               ` Michael S. Tsirkin
2017-11-29  9:11                 ` Paolo Bonzini
2017-11-29 10:21                   ` Tan, Jianfeng
2017-11-28 19:15         ` Michael S. Tsirkin
2017-11-28  9:03 ` [Qemu-devel] [PATCH 4/4] cryptodev-vhost-user: set the key length Gonglei
2017-11-28 10:10 ` [Qemu-devel] [PATCH 0/4] cryptodev: add vhost support no-reply
2017-12-18  9:03 ` Gonglei (Arei)
2017-12-20 17:38   ` Michael S. Tsirkin
2017-12-21  0:51     ` Gonglei (Arei)
2017-12-21  4:28       ` Michael S. Tsirkin
2017-12-21  9:11       ` Paolo Bonzini
2017-12-21 14:25 ` Michael S. Tsirkin
2017-12-22  7:39   ` Gonglei (Arei)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b98e2b09-35e7-47c2-b49f-982a09804b4f@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=jianjay.zhou@huawei.com \
    --cc=longpeng2@huawei.com \
    --cc=mst@redhat.com \
    --cc=pasic@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=roy.fan.zhang@intel.com \
    --cc=stefanha@redhat.com \
    --cc=weidong.huang@huawei.com \
    --cc=xin.zeng@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).