From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 895E6968 for ; Tue, 9 Aug 2016 17:15:51 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP; 09 Aug 2016 08:15:48 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,494,1464678000"; d="scan'208,217";a="1032482078" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by orsmga002.jf.intel.com with ESMTP; 09 Aug 2016 08:15:46 -0700 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.183]) by IRSMSX102.ger.corp.intel.com ([169.254.2.123]) with mapi id 14.03.0248.002; Tue, 9 Aug 2016 16:15:43 +0100 From: "Trahe, Fiona" To: David Griswold , "users@dpdk.org" CC: "Trahe, Fiona" Thread-Topic: Crypto Framework with QAT Device Thread-Index: AQHR8kjfZ7rNf1o7zUWi2i0J5EnAy6BAritw Date: Tue, 9 Aug 2016 15:15:42 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B4358907B4A9@IRSMSX101.ger.corp.intel.com> References: <348A99DA5F5B7549AA880327E580B4358907B371@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: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNDM2NWFhOTItYzk2Yy00NmI5LTkwYjMtYzg4MzE4YWQxMjRhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IkhnSjhFa3N5dTlPZDY0WWpuNzU1aWpwZHhDSUd6akthNnUreis2MVZlMlE9In0= x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] 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-users] Crypto Framework with QAT Device X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2016 15:15:52 -0000 Yes, you're correct re the Atom device. By ADF driver API I assume you mean the QuickAssisst API. The purpose of the cryptodev framework was to provide a generic API, which = could pass crypto requests to SW and HW (QuickAssist and other) devices. Th= e QuickAssist API has a lot of QuickAssist-specific parameters, so was not = a good match for this. As to why the QuickAssist API and user-space driver were not used below the= cryptodev layer there are a number of reasons including performance, codin= g standards, simpler configuration, a desire to take advantage of dpdk feat= ures like memory handling, pci device discovery, etc Fiona From: David Griswold [mailto:DGriswold@advaoptical.com] Sent: Tuesday, August 9, 2016 3:18 PM To: Trahe, Fiona ; users@dpdk.org Subject: RE: Crypto Framework with QAT Device Thanks Fiona, Unfortunately, I'm wanting to run on C2xxx (Atom) devices. I don't believe= any of these SKUs have the newer QAT device. Is that correct? I did get it working with the QAT sample application as you point out. Just for context, could you explain why the cryptodev framework did not use= the ADF driver's API, like the QAT sample uses? I suspect it had to do with performance but perhaps the API is limiting in = some way? Thanks for your help, David From: Trahe, Fiona [mailto:fiona.trahe@intel.com] Sent: Tuesday, August 09, 2016 10:08 AM To: users@dpdk.org; David Griswold > Cc: Trahe, Fiona > Subject: re: Crypto Framework with QAT Device Hi David, The cryptodev framework can't be used with the earlier QuickAssist devices.= (8900-8920) Even if you got past the differing CSRs the firmware interface is significa= ntly different, so a complete rewrite of the code which builds the message descriptors would be = necessary. Sorry, that's probably not what you wanted to hear. A dpdk sample app wrapping the released Intel QuickAssist driver was develo= ped prior to the cryptodev framework: http://dpdk.org/doc/guides/sample_app_ug/intel_quickassist.html?highlight= =3Dquickassist A better alternative would be to move to one of the newer QuickAssist devic= es, is that an option? Regards, Fiona Hello, I'd like to use the crypto framework with an older QAT device from the 8900= -8920 (QAT1.5) series. The current support is for the 8925-8955 series (QAT1.6). I've installed the ADF software and gotten the crypto framework to recogniz= e the PCIe device, but the BAR register layout seems to be different from what the framework i= s expecting when it goes to create the queue pairs. Could the experts comment on how difficult this would be and if possible wh= at my next steps might be? Thanks in advance for your advice, David