From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 096C8F94 for ; Thu, 27 Apr 2017 13:50:36 +0200 (CEST) Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Apr 2017 04:50:22 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.37,383,1488873600"; d="scan'208,217";a="94821753" Received: from irsmsx110.ger.corp.intel.com ([163.33.3.25]) by fmsmga006.fm.intel.com with ESMTP; 27 Apr 2017 04:50:21 -0700 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.187]) by irsmsx110.ger.corp.intel.com ([169.254.15.151]) with mapi id 14.03.0319.002; Thu, 27 Apr 2017 12:50:20 +0100 From: "Trahe, Fiona" To: Aravamudan Srivathsan , "dev@dpdk.org" CC: "Doherty, Declan" , "Trahe, Fiona" Thread-Topic: OpenSSL Cryptodev PMD and openssl engine Thread-Index: AQHSvmGSnYRpZRHM60GD6gL1Vl9cBqHXz1mQgACL+ACAAL2tcA== Date: Thu, 27 Apr 2017 11:50:20 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B435891EB910@IRSMSX101.ger.corp.intel.com> References: <5E2018A4-BCC8-4D0A-AD95-A70883D28997@technicolor.com>, <348A99DA5F5B7549AA880327E580B435891EB092@IRSMSX101.ger.corp.intel.com> In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [163.33.239.182] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] OpenSSL Cryptodev PMD and openssl engine X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Apr 2017 11:50:37 -0000 Hi Srivathsan, From: Aravamudan Srivathsan [mailto:Srivathsan.Aravamudan@technicolor.com] Sent: Thursday, April 27, 2017 2:20 AM To: Trahe, Fiona ; dev@dpdk.org Cc: Doherty, Declan Subject: Re: OpenSSL Cryptodev PMD and openssl engine Hi Fiona, Thank you for the reply. I have a crypto device that is connected to PCI. It can do standard crypto = operations like AES, DES, and so on. I have openssl engine (a plugin) for this. Our environment is We have DPDK application for routing, forwarding, IPSec etc. (All routing a= nd tunnelling) We also have IoT application which would like to use the Openssl for doing = some crypto operations. My intention is 1. To use the existing openssl infrastructure (without writing the crypto P= MD) to use the hardware acclearation. 2. Share the same device not only for doing the IPsec but also for doing cr= ypto operations outside the DPDK EAL. Yes the OpenSSL will have extra layer and do a copy of buffer, but the cryp= to operations will still happen in the driver. [Fiona] There would be other development effort needed. It's probably not a= seamless port, as the openssl engine infrastructure isn't in the OpenSSL PMD. The PMD is just= a wrapper for the calls to the encryption APIs. Engines in OpenSSL go through a phase of init to load the = engine dynamic object. You would probably need to port large sections of th= is code to the init sequences of the PMD. It's not clear how or if this wou= ld fit in the PMD. This is on top of the performance issues already mention= ed. Let me know if i make sense. Srivathsan ________________________________ From: Trahe, Fiona > Sent: Wednesday, April 26, 2017 9:52 PM To: Aravamudan Srivathsan; dev@dpdk.org Cc: Trahe, Fiona; Doherty, Declan Subject: RE: OpenSSL Cryptodev PMD and openssl engine ** WARNING: This mail is from an external source ** Hi Srivathsan, > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Aravamudan > Srivathsan > Sent: Wednesday, April 26, 2017 8:49 AM > To: dev@dpdk.org > Subject: [dpdk-dev] OpenSSL Cryptodev PMD and openssl engine > > Hi All, > > We have a openssl engine available. Is it possible to use the openssl Cry= pto > PMD to do the hardware offloading? I am trying to see if i can avoid writ= ing > the cryptopmd also to reuse the use of the device shared between the DPDK > and other process. > > Thank you > Srivathsan It might be possible to plug your openssl engine in below the openssl PMD, but you would lose the advantage of offloading bursts to the hardware and would add an extra translation layer on the data path so it would likely not be a performant solution. Can you clarify a little how you want to share the device? i.e. is the other process using the device directly with openssl and is the DPDK= process for IPSec or is this also for ssl?