[v2,0/2] vhost/crypto: fix initialization
Message ID | 20201002153601.84097-1-roy.fan.zhang@intel.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3876CA04BA; Fri, 2 Oct 2020 17:36:36 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 1E0471D97C; Fri, 2 Oct 2020 17:36:15 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id E3D0D1D6F6; Fri, 2 Oct 2020 17:36:11 +0200 (CEST) IronPort-SDR: ZRIFmV68ncRjx9KzQr4bBH6Ym8Pz6voqp/wOQBg3eTP7uug+b3N4rbgKPK8ASVOLgACGYTGfIT AYlrFq/HwiiQ== X-IronPort-AV: E=McAfee;i="6000,8403,9762"; a="247754173" X-IronPort-AV: E=Sophos;i="5.77,328,1596524400"; d="scan'208";a="247754173" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga105.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Oct 2020 08:36:06 -0700 IronPort-SDR: BPUGJzPCA0NSy5xKfz0P/G8VeXaM0zpUS8EF37s65Esx8QDXEPSgOasIWNvGFw/jJhKnXJAsEM lCo+VHk5K3hg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.77,328,1596524400"; d="scan'208";a="515193792" Received: from silpixa00398673.ir.intel.com (HELO silpixa00398673.ger.corp.intel.com) ([10.237.223.136]) by fmsmga006.fm.intel.com with ESMTP; 02 Oct 2020 08:36:04 -0700 From: Fan Zhang <roy.fan.zhang@intel.com> To: dev@dpdk.org Cc: chenbo.xia@intel.com, maxime.coquelin@redhat.com, changpeng.liu@intel.com, ferruh.yigit@intel.com, stable@dpdk.org, Fan Zhang <roy.fan.zhang@intel.com> Date: Fri, 2 Oct 2020 16:35:59 +0100 Message-Id: <20201002153601.84097-1-roy.fan.zhang@intel.com> X-Mailer: git-send-email 2.20.1 In-Reply-To: <20201002083615.45470-1-roy.fan.zhang@intel.com> References: <20201002083615.45470-1-roy.fan.zhang@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: [dpdk-dev] [dpdk-dev v2 0/2] vhost/crypto: fix initialization 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://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Message
Fan Zhang
Oct. 2, 2020, 3:35 p.m. UTC
This patch fixes the problem that vhost crypto cannot be initialized due to the different requirement between built-in virtio-net and virtio-crypto. The fix includes the following change: - Added new internal enum type virtio_backend_type to distinguish virtio-net, virtio-crypto, and external device types. - Added new API rte_vhost_crypto_driver_start to distinguish between virtio-net and virtio-crypto built-in drivers initialization. v2: - Removed socket.c setting vhost crypto features. - Fixed incorrect feature flag. - Rebased on top of latest master. Fan Zhang (2): vhost: add backend type in driver start vhost/crypto: fix feature negotiation examples/vhost_crypto/main.c | 3 +- lib/librte_vhost/rte_vhost_crypto.h | 12 ++++++++ lib/librte_vhost/rte_vhost_version.map | 1 + lib/librte_vhost/socket.c | 39 +++++++++++++++++++----- lib/librte_vhost/vhost_crypto.c | 41 +++++++++++++++++--------- lib/librte_vhost/vhost_user.h | 8 +++++ 6 files changed, 81 insertions(+), 23 deletions(-)