From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id BDD84A498 for ; Wed, 9 May 2018 12:33:05 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 May 2018 03:33:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,381,1520924400"; d="scan'208";a="38560840" Received: from irsmsx107.ger.corp.intel.com ([163.33.3.99]) by fmsmga008.fm.intel.com with ESMTP; 09 May 2018 03:33:03 -0700 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.179]) by IRSMSX107.ger.corp.intel.com ([169.254.10.141]) with mapi id 14.03.0319.002; Wed, 9 May 2018 11:33:02 +0100 From: "Trahe, Fiona" To: Shally Verma , "De Lara Guarch, Pablo" CC: "Doherty, Declan" , "pathreya@caviumnetworks.com" , "ssahu@caviumnetworks.com" , "agupta@caviumnetworks.com" , "dev@dpdk.org" , Sunila Sahu , Ashish Gupta , "Trahe, Fiona" Thread-Topic: [PATCH v2 5/6] crypto/openssl: add asym crypto support Thread-Index: AQHTzNDuO0+MnT3ioU+gXDMPFwFaw6QnZwDw Date: Wed, 9 May 2018 10:33:01 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B4358947D9A6@IRSMSX103.ger.corp.intel.com> References: <1522927489-23668-1-git-send-email-shally.verma@caviumnetworks.com> <1522927489-23668-6-git-send-email-shally.verma@caviumnetworks.com> In-Reply-To: <1522927489-23668-6-git-send-email-shally.verma@caviumnetworks.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMTY3ZDZiY2EtMzk1Mi00YTg4LTk5MmUtNDdjZmE1NmU1ZjEzIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6InBRNkF4XC8yOWc0T29mcW8zSk5pQ3M3NmVFOFZUemR6dkxLQktpd0dxb2tBPSJ9 x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.200.100 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v2 5/6] crypto/openssl: add asym crypto support 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: Wed, 09 May 2018 10:33:06 -0000 Hi Shally,=20 > -----Original Message----- > From: Shally Verma [mailto:shally.verma@caviumnetworks.com] > Sent: Thursday, April 5, 2018 12:25 PM > To: De Lara Guarch, Pablo > Cc: Doherty, Declan ; Trahe, Fiona ; > pathreya@caviumnetworks.com; ssahu@caviumnetworks.com; agupta@caviumnetwo= rks.com; > dev@dpdk.org; Sunila Sahu ; Ashish Gupta > > Subject: [PATCH v2 5/6] crypto/openssl: add asym crypto support >=20 > Add asymmetric crypto operation support in openssl PMD. > Current list of supported asym xforms: > * RSA > * DSA > * Deffie-hellman > * Modular Operations [Fiona] What was your rationale for adding this into the openssl PMD vs cre= ating a new openssl_asym PMD? Will this work ok if there's a burst of ops including asym and sym operatio= ns enqueued to the same qp?