From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 00/12] lib/librte_vhost: introduce new vhost_user crypto Date: Sat, 20 Jan 2018 16:53:11 +0100 Message-ID: <1731230.NST0VfsklJ@xps> References: <20171127200115.31049-1-roy.fan.zhang@intel.com> <20180118145952.GN29540@yliu-mob> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org, Yuanhan Liu , maxime.coquelin@redhat.com, tiwei.bie@intel.com, ferruh.yigit@intel.com, pablo.de.lara.guarch@intel.com To: Fan Zhang Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 1D3DA2951 for ; Sat, 20 Jan 2018 16:53:48 +0100 (CET) In-Reply-To: <20180118145952.GN29540@yliu-mob> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 18/01/2018 15:59, Yuanhan Liu: > On Mon, Nov 27, 2017 at 08:01:03PM +0000, Fan Zhang wrote: > > This patchset adds crypto backend suppport to vhost_user library, > > including a proof-of-concept sample application. The implementation > > follows the virtio-crypto specification and have been tested > > with qemu 2.9.50 (with several patches applied, detailed later) > > with Fedora 24 running in the frontend. > > > > The vhost_user library acts as a "bridge" method that translate > > the virtio-crypto crypto requests to DPDK crypto operations, so it > > is purely software implementation. However it does require the user > > to provide the DPDK Cryptodev ID so it knows how to handle the > > virtio-crypto session creation and deletion mesages. > > > > Currently the implementation supports AES-CBC-128 and HMAC-SHA1 > > cipher only/chaining modes and does not support sessionless mode > > yet. The guest can use standard virtio-crypto driver to set up > > session and sends encryption/decryption requests to backend. The > > vhost-crypto sample application provided in this patchset will > > do the actual crypto work. > > > > To make this patchset working, a few tweaks need to be done: > > > > In the host: > > 1. Download the qemu source code, and apply the patches in: > > list.nongnu.org/archive/html/qemu-devel/2017-07/msg04664.html. > > I could not open it. What's the status of them now? Have they got > merged? As usual, we must wait to have Qemu support ready. How this work is related to drivers/crypto/virtio/ proposed by Jay Zhou (Huawei)?