From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0138.outbound.protection.outlook.com [104.47.32.138]) by dpdk.org (Postfix) with ESMTP id 4F8DE298F for ; Thu, 27 Apr 2017 03:20:17 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=technicolor.onmicrosoft.com; s=selector1-technicolor-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=c4R8l4V75yyHxrAjqGAkbyTzNugG54GQsCnHOWozuTs=; b=TlDxMmSLQrAvYW24Jr2/uRsosqXcvAHNFrs8NwBf9mqYHH2KPt2m8Bw6eN2JXaPBrWha7fHEH6iMiLol98avunUX63IVKf7/1BwubxsOSnstGjwLQf5OXgKliJLQ4N5sU8GfeJSri/MjvJ21wdH4MI9U+oikMuyD1OgVs2OV8WA= Received: from DM5PR02MB2315.namprd02.prod.outlook.com (10.168.174.139) by DM5PR02MB2315.namprd02.prod.outlook.com (10.168.174.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1061.12; Thu, 27 Apr 2017 01:20:14 +0000 Received: from DM5PR02MB2315.namprd02.prod.outlook.com ([10.168.174.139]) by DM5PR02MB2315.namprd02.prod.outlook.com ([10.168.174.139]) with mapi id 15.01.1061.011; Thu, 27 Apr 2017 01:20:14 +0000 From: Aravamudan Srivathsan To: "Trahe, Fiona" , "dev@dpdk.org" CC: "Doherty, Declan" Thread-Topic: OpenSSL Cryptodev PMD and openssl engine Thread-Index: AQHSvmGScpNzSD2AjUKv4WaI9PzASaHX1cWAgACUSSY= Date: Thu, 27 Apr 2017 01:20:14 +0000 Message-ID: References: <5E2018A4-BCC8-4D0A-AD95-A70883D28997@technicolor.com>, <348A99DA5F5B7549AA880327E580B435891EB092@IRSMSX101.ger.corp.intel.com> In-Reply-To: <348A99DA5F5B7549AA880327E580B435891EB092@IRSMSX101.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: intel.com; dkim=none (message not signed) header.d=none;intel.com; dmarc=none action=none header.from=technicolor.com; x-originating-ip: [25.168.111.132] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; DM5PR02MB2315; 7:tl3mYo7KOOpvgNkCSapLsQti18Y98zvCABhTiP69w7scgcQLABEhq91vxDWjG2OTVYrf15tSaizkB8cXL6Qzeolw3tBq8tK7HIdheIa/qHhLOEvi5TUOtmENcIGu27zkO79x27N2zbpJ/LCmAsoWE1v9Uvfhe6P1disRr1SieWAHKtzNXDKdeXOqU5WYDT1TsKjJ8GLHAsNK1HVHZv6ivNqHexZvQ2q000CSXQFgdyE7RNdPCW3oM0tMk+YpMH+I+rNQyMj3uZtJiJu+xnxIjnZXLCRCpfY1D6tyKfw9aPlk0BO4M65dVZmARLqx06EsfX+RiHJzxPjZJoK3IRGWAw==; 20:9oVwY+H6VuC9jIngqaZsxz3+e3B2QSzOrz1UYSdj9ulwnBZpU258Z8uw2vX7E1y4zScgjRP0kikBw3SQqNmcXo1+pU7+9SnLN+oIguF52r3jXE0BH5qCVyEQbXNdPCAaZUpgZk0WIRs4TZ9aeNGCxnfBxLHp3RQz2BdPJBWoTkA= x-ms-office365-filtering-correlation-id: 3651dab2-ba2a-4d56-bbc6-08d48d0b8ee1 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081)(201703131423075)(201703031133081); SRVR:DM5PR02MB2315; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(228905959029699); x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(6055026)(6041248)(20161123558100)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123560025)(20161123564025)(6072148); SRVR:DM5PR02MB2315; BCL:0; PCL:0; RULEID:; SRVR:DM5PR02MB2315; x-forefront-prvs: 029097202E x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39410400002)(39850400002)(39400400002)(39450400003)(39860400002)(39840400002)(13464003)(377454003)(53754006)(2950100002)(122556002)(86362001)(50986999)(54356999)(76176999)(66066001)(38730400002)(7696004)(236005)(6606003)(2501003)(229853002)(9686003)(3660700001)(54896002)(2906002)(4326008)(345774005)(3280700002)(5660300001)(8936002)(6506006)(6116002)(6246003)(25786009)(77096006)(55016002)(19627405001)(74316002)(102836003)(33656002)(3846002)(53546009)(6436002)(81166006)(2900100001)(7736002)(189998001)(99286003)(8676002)(53936002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR02MB2315; H:DM5PR02MB2315.namprd02.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM MIME-Version: 1.0 X-OriginatorOrg: technicolor.com X-MS-Exchange-CrossTenant-originalarrivaltime: 27 Apr 2017 01:20:14.5991 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 036da35c-ba43-4e4a-9bff-72ec0f508621 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR02MB2315 Content-Type: text/plain; charset="iso-8859-1" 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 01:20:17 -0000 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. 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?