From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by dpdk.org (Postfix) with ESMTP id 886387CDC for ; Fri, 19 Oct 2018 02:05:17 +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 fmsmga107.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Oct 2018 17:05:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,397,1534834800"; d="scan'208";a="79879586" Received: from irsmsx102.ger.corp.intel.com ([163.33.3.155]) by fmsmga008.fm.intel.com with ESMTP; 18 Oct 2018 17:05:15 -0700 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.4]) by IRSMSX102.ger.corp.intel.com ([169.254.2.67]) with mapi id 14.03.0319.002; Fri, 19 Oct 2018 01:05:14 +0100 From: "Trahe, Fiona" To: "Pathak, Pravin" , "users@dpdk.org" Thread-Topic: Crypto QAT device not found Thread-Index: AdRnKRXD20Lii5N3ToKo7aE94IX7JwAEow1w Date: Fri, 19 Oct 2018 00:05:14 +0000 Message-ID: <348A99DA5F5B7549AA880327E580B435896503E4@IRSMSX101.ger.corp.intel.com> References: <168A68C163D584429EF02A476D527442490F5F60@FMSMSX108.amr.corp.intel.com> In-Reply-To: <168A68C163D584429EF02A476D527442490F5F60@FMSMSX108.amr.corp.intel.com> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMzZkNWUxZmMtM2Q5NC00ODFiLTk5YjMtMzY1OTYxMTA5MDM2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiTUFxUGpOXC9ncGREa0RHRitFc2lwM1ZKbFpiUUhOM1U0YTBkRUQySVZNbVd3VjdpVnorbDY2SDg4Qm80NXh4S3QifQ== x-ctpclassification: CTP_NT dlp-product: dlpe-windows dlp-version: 11.0.400.15 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-users] Crypto QAT device not found X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2018 00:05:18 -0000 Hi Pravin, See below. > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Pathak, Pravin > Sent: Thursday, October 18, 2018 2:30 PM > To: users@dpdk.org > Subject: [dpdk-users] Crypto QAT device not found >=20 > Hi All - > I have server with Intel QAT c62x device. I followed all documentation. >=20 > - Rebuild DPDK to use QAT >=20 > - QAT drivers are loaded. >=20 > - QAT devices are bound to DPDK >=20 >=20 > Crypto devices using DPDK-compatible driver > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > 0000:3d:01.0 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:01.1 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:01.2 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:01.3 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:01.4 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:01.5 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:01.6 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:01.7 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:02.0 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:02.1 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci > 0000:3d:02.2 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf,vfio-pci >=20 > But if I use l2fwd-crypto sample, I get no crypto device found error >=20 > Checking link statusdone > Port0 Link Up. Speed 1000 Mbps - full-duplex > Port1 Link Up. Speed 1000 Mbps - full-duplex > Lcore 0: RX port 0 > Lcore 1: RX port 1 > No crypto devices available > EAL: Error - exiting with code: 1 > Cause: Failed to initialize crypto devices >=20 > It works if I add virtual device --vdev "crypto_aesni_mb0" but I am not = able to use HW device. > Your help is appreciated. >=20 > Thanks > Pravin [Fiona] I haven't used this tool for a while, but the command line options = should be similar to the=20 dpdk-test-crypto-perf tool. For that for QAT you should whitelist the devic= e. e.g.: -w 0000:3d:01.0 ( before the -- , i.e. it's an EAL parameter)=20 and use --devtype crypto_qat (after the -- , it's a parameter for the app= lication). The terminology of --vdev changed in a recent release, so refer to the vers= ion of =20 http://doc.dpdk.org/guides/sample_app_ug/l2_forward_crypto.html for the cmdline options appropriate to the release you're using. -cdev_type HW should also cause it to select QAT