From: Jay Zhou <jianjay.zhou@huawei.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
"Huangweidong (C)" <weidong.huang@huawei.com>,
"stefanha@redhat.com" <stefanha@redhat.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>,
"Gonglei (Arei)" <arei.gonglei@huawei.com>,
"wangxin (U)" <wangxinxin.wang@huawei.com>
Subject: Re: [Qemu-devel] [PATCH v6 0/4] cryptodev: add vhost support
Date: Fri, 2 Feb 2018 09:06:04 +0800 [thread overview]
Message-ID: <5A73B97C.2080600@huawei.com> (raw)
In-Reply-To: <20180201190537-mutt-send-email-mst@kernel.org>
On 2018/2/2 1:06, Michael S. Tsirkin wrote:
> Yes, I plan to merge it in the next pull.
> Pls don't assume anything until it's merged upstream though,
> some issues surface late.
>
Okay, I see. Thanks for reviewing!
Regards,
Jay
> On Thu, Feb 01, 2018 at 11:29:15AM +0000, Zhoujian (jay) wrote:
>> Hi Michael,
>> I am wondering whether this version is OK for you?
>> Any comment will be appreciated, thanks.
>>
>> Regards,
>> Jay
>>
>>> -----Original Message-----
>>> From: Zhoujian (jay)
>>> Sent: Sunday, January 21, 2018 8:55 PM
>>> To: qemu-devel@nongnu.org
>>> Cc: mst@redhat.com; pbonzini@redhat.com; Huangweidong (C)
>>> <weidong.huang@huawei.com>; stefanha@redhat.com; Zhoujian (jay)
>>> <jianjay.zhou@huawei.com>; pasic@linux.vnet.ibm.com; longpeng
>>> <longpeng2@huawei.com>; xin.zeng@intel.com; roy.fan.zhang@intel.com; Gonglei
>>> (Arei) <arei.gonglei@huawei.com>; wangxin (U) <wangxinxin.wang@huawei.com>
>>> Subject: [PATCH v6 0/4] cryptodev: add vhost support
>>>
>>> From: Gonglei <arei.gonglei@huawei.com>
>>>
>>> I posted the RFC verion a few months ago for DPDK vhost-crypto implmention,
>>> and now it's time to send the formal version. Because we need an user space
>>> scheme for better performance.
>>>
>>> The vhost user crypto server side patches had been sent to DPDK community,
>>> pls see
>>>
>>> [RFC PATCH 0/6] lib/librte_vhost: introduce new vhost_user crypto backend
>>> support http://dpdk.org/ml/archives/dev/2017-November/081048.html
>>>
>>> You also can get virtio-crypto polling mode driver from:
>>>
>>> [PATCH] virtio: add new driver for crypto devices
>>> http://dpdk.org/ml/archives/dev/2017-November/081985.html
>>>
>>> v5 -> v6:
>>> Fix compile error about backends/cryptodev-vhost-user.o and rebase on
>>> the master
>>> v4 -> v5:
>>> squash [PATCH v4 5/5] into previous patches [Michael]
>>> v3 -> v4:
>>> "[PATCH v4 5/5] cryptodev-vhost-user: depend on CONFIG_VHOST_CRYPTO
>>> and CONFIG_VHOST_USER" newly added to fix compilation dependency [Michael]
>>> v2 -> v3:
>>> New added vhost user messages should be sent only when feature
>>> has been successfully negotiated [Michael]
>>> v1 -> v2:
>>> Fix compile error on mingw32
>>>
>>> Gonglei (4):
>>> cryptodev: add vhost-user as a new cryptodev backend
>>> cryptodev: add vhost support
>>> cryptodev-vhost-user: add crypto session handler
>>> cryptodev-vhost-user: set the key length
>>>
>>> backends/Makefile.objs | 6 +
>>> backends/cryptodev-builtin.c | 1 +
>>> backends/cryptodev-vhost-user.c | 379
>>> ++++++++++++++++++++++++++++++++++
>>> backends/cryptodev-vhost.c | 347 +++++++++++++++++++++++++++++++
>>> configure | 15 ++
>>> docs/interop/vhost-user.txt | 26 +++
>>> hw/virtio/Makefile.objs | 2 +-
>>> hw/virtio/vhost-user.c | 104 ++++++++++
>>> hw/virtio/virtio-crypto.c | 70 +++++++
>>> include/hw/virtio/vhost-backend.h | 8 +
>>> include/hw/virtio/virtio-crypto.h | 1 +
>>> include/sysemu/cryptodev-vhost-user.h | 47 +++++
>>> include/sysemu/cryptodev-vhost.h | 154 ++++++++++++++
>>> include/sysemu/cryptodev.h | 8 +
>>> qemu-options.hx | 21 ++
>>> vl.c | 6 +
>>> 16 files changed, 1194 insertions(+), 1 deletion(-) create mode 100644
>>> backends/cryptodev-vhost-user.c create mode 100644 backends/cryptodev-
>>> vhost.c create mode 100644 include/sysemu/cryptodev-vhost-user.h
>>> create mode 100644 include/sysemu/cryptodev-vhost.h
>>>
>>> --
>>> 1.8.3.1
>>>
>
> .
>
next prev parent reply other threads:[~2018-02-02 1:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-21 12:54 [Qemu-devel] [PATCH v6 0/4] cryptodev: add vhost support Jay Zhou
2018-01-21 12:54 ` [Qemu-devel] [PATCH v6 1/4] cryptodev: add vhost-user as a new cryptodev backend Jay Zhou
2018-02-13 16:46 ` Michael S. Tsirkin
2018-02-14 2:30 ` Zhoujian (jay)
2018-01-21 12:54 ` [Qemu-devel] [PATCH v6 2/4] cryptodev: add vhost support Jay Zhou
2018-02-13 16:44 ` Michael S. Tsirkin
2018-02-14 2:54 ` Zhoujian (jay)
2018-01-21 12:54 ` [Qemu-devel] [PATCH v6 3/4] cryptodev-vhost-user: add crypto session handler Jay Zhou
2018-01-21 12:54 ` [Qemu-devel] [PATCH v6 4/4] cryptodev-vhost-user: set the key length Jay Zhou
2018-02-01 11:29 ` [Qemu-devel] [PATCH v6 0/4] cryptodev: add vhost support Zhoujian (jay)
2018-02-01 17:06 ` Michael S. Tsirkin
2018-02-02 1:06 ` Jay Zhou [this message]
2018-02-13 16:47 ` Michael S. Tsirkin
2018-02-14 2:35 ` Zhoujian (jay)
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=5A73B97C.2080600@huawei.com \
--to=jianjay.zhou@huawei.com \
--cc=arei.gonglei@huawei.com \
--cc=longpeng2@huawei.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=roy.fan.zhang@intel.com \
--cc=stefanha@redhat.com \
--cc=wangxinxin.wang@huawei.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).