From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 6AC07A2E1B for ; Wed, 4 Sep 2019 15:06:55 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 7B5BF1EDC3; Wed, 4 Sep 2019 15:06:54 +0200 (CEST) Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by dpdk.org (Postfix) with ESMTP id F1B411ED89 for ; Wed, 4 Sep 2019 15:06:52 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by orsmga106.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 04 Sep 2019 06:06:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,467,1559545200"; d="scan'208";a="212384715" Received: from irsmsx109.ger.corp.intel.com ([163.33.3.23]) by fmsmga002.fm.intel.com with ESMTP; 04 Sep 2019 06:06:50 -0700 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.61]) by IRSMSX109.ger.corp.intel.com ([169.254.13.11]) with mapi id 14.03.0439.000; Wed, 4 Sep 2019 14:06:50 +0100 From: "Zhang, Roy Fan" To: Akhil Goyal , "dev@dpdk.org" CC: "Ananyev, Konstantin" , "Doherty, Declan" , "De Lara Guarch, Pablo" Thread-Topic: [RFC PATCH 1/9] security: introduce CPU Crypto action type and API Thread-Index: AQHVYm4YTD6+9RxOHE+pmjY8VoDMaqcbQpEAgAAy7FA= Date: Wed, 4 Sep 2019 13:06:49 +0000 Message-ID: <9F7182E3F746AB4EA17801C148F3C6043369D686@IRSMSX101.ger.corp.intel.com> References: <20190903154046.55992-1-roy.fan.zhang@intel.com> <20190903154046.55992-2-roy.fan.zhang@intel.com> In-Reply-To: Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNWFjZjI4NWMtOTQ1MS00NzRjLTg0M2MtYzcyMDc5NjBkYjRiIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiZkxnTHFVS0ZydVErY25nbERGeEZFeUx1MStVVzYzUzZUWWlPVGhsVTY5cjM1dlQ2QWtJS3lCMjl5NkpXTkI0OCJ9 dlp-product: dlpe-windows dlp-version: 11.2.0.6 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] [RFC PATCH 1/9] security: introduce CPU Crypto action type and API 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hi Akhil, This action type allows the burst of symmetric crypto workload using the sa= me algorithm, key, and direction being processed by CPU cycles synchronously.= =20 This flexible action type does not require external hardware involvement, having the crypto workload processed synchronously, and is more performant than Cryptodev SW PMD due to the saved cycles on removed "async mode simulation" as well as 3 cacheline access of the crypto ops.=20 AESNI-GCM and AESNI-MB PMDs are updated with this support. There is a small performance test app under app/test/security_aesni_gcm(mb)_perftest to prove. For the new API The packet is sent to the crypto device for symmetric crypto processing. The device will encrypt or decrypt the buffer based on the sess= ion data specified and preprocessed in the security session. Different than the inline or lookaside modes, when the function exits, the user will expect the buffers are either processed successfully, or having the error n= umber assigned to the appropriate index of the status array. Will update the program's guide in the v1 patch. Regards, Fan > -----Original Message----- > From: Akhil Goyal [mailto:akhil.goyal@nxp.com] > Sent: Wednesday, September 4, 2019 11:33 AM > To: Zhang, Roy Fan ; dev@dpdk.org > Cc: Ananyev, Konstantin ; Doherty, Declan > ; De Lara Guarch, Pablo > > Subject: RE: [RFC PATCH 1/9] security: introduce CPU Crypto action type a= nd > API >=20 > Hi Fan, >=20 > > > > This patch introduce new RTE_SECURITY_ACTION_TYPE_CPU_CRYPTO > action > > type to security library. The type represents performing crypto > > operation with CPU cycles. The patch also includes a new API to > > process crypto operations in bulk and the function pointers for PMDs. > > > I am not able to get the flow of execution for this action type. Could yo= u > please elaborate the flow in the documentation. If not in documentation > right now, then please elaborate the flow in cover letter. > Also I see that there are new APIs for processing crypto operations in bu= lk. > What does that mean. How are they different from the existing APIs which > are also handling bulk crypto ops depending on the budget. >=20 >=20 > -Akhil