From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@monjalon.net>
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com
 [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 1D3DA2951
 for <dev@dpdk.org>; Sat, 20 Jan 2018 16:53:48 +0100 (CET)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
 by mailout.nyi.internal (Postfix) with ESMTP id BEE2E20A8F;
 Sat, 20 Jan 2018 10:53:47 -0500 (EST)
Received: from frontend2 ([10.202.2.161])
 by compute1.internal (MEProxy); Sat, 20 Jan 2018 10:53:47 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h=
 cc:content-transfer-encoding:content-type:date:from:in-reply-to
 :message-id:mime-version:references:subject:to:x-me-sender
 :x-me-sender:x-sasl-enc; s=mesmtp; bh=gc4dOQd2RqLqviGXX8IuGkOIUy
 fdzz/hVGcFqbM6C/E=; b=POX/ZXWsjx4HhkMtIZ+XzIdjRvAUMF0q+1gdDR48iW
 WkqWs3Vr4Ff67d4XtdGZpNDO3y3MRzmh3k7P6eoDkuctyOQeTWbDxK0MtTIsYTam
 jWmF2vAVDP6jxNs/RFEpiyc/Fq5q3ZsabkjiQA6IWKibShbtTLlN3VXubgwvwkfp
 w=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=
 messagingengine.com; h=cc:content-transfer-encoding:content-type
 :date:from:in-reply-to:message-id:mime-version:references
 :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=gc4dOQ
 d2RqLqviGXX8IuGkOIUyfdzz/hVGcFqbM6C/E=; b=ZOA0mwy8SakGKkR8VroMEH
 xLrJYq4IbAsAPHVwvNpM1+l8zftXr881f+v3ssj2z62yhp3WQBwaJLuKvtlIuF/y
 cKnrt/R1td7+dpjQIWkbhVZSkDI8nVv9BCWSgjhZntRSEDRE3U2QBzzMMESWDx/z
 4/4kPmw2UK6z5xEfzCT1gnz+B+8EMEkt3LVkOj+xBRR0+fBgxGErv6wSgi085oWA
 xsR+3JZJeN4o9bfOLmt7eUqh01ajUwRfyJbbfntphENJYWVPNeXkJUmfu+XpwBAV
 v8t6cKTNtbaF+bBs+NnxUx7+PhkSUzccZh3ODYhgr9nVDc3b1d/3POFXKCbS9Vwg
 ==
X-ME-Sender: <xms:C2ZjWqNPqJMkKKabkOgaPZ-AIx-yN7Z4hf0VkPYdgW6IxgwjqajPWQ>
Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184])
 by mail.messagingengine.com (Postfix) with ESMTPA id 7060A24771;
 Sat, 20 Jan 2018 10:53:47 -0500 (EST)
From: Thomas Monjalon <thomas@monjalon.net>
To: Fan Zhang <roy.fan.zhang@intel.com>
Cc: dev@dpdk.org, Yuanhan Liu <yliu@fridaylinux.org>,
 maxime.coquelin@redhat.com, tiwei.bie@intel.com, ferruh.yigit@intel.com,
 pablo.de.lara.guarch@intel.com
Date: Sat, 20 Jan 2018 16:53:11 +0100
Message-ID: <1731230.NST0VfsklJ@xps>
In-Reply-To: <20180118145952.GN29540@yliu-mob>
References: <20171127200115.31049-1-roy.fan.zhang@intel.com>
 <20180118145952.GN29540@yliu-mob>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [dpdk-dev] [PATCH 00/12] lib/librte_vhost: introduce new
	vhost_user crypto
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jan 2018 15:53:48 -0000

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)?