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 9DBDD1B1EC for ; Fri, 19 Oct 2018 20:26:15 +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 orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Oct 2018 11:26:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,401,1534834800"; d="scan'208";a="80082551" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga008.fm.intel.com with ESMTP; 19 Oct 2018 11:26:14 -0700 Received: from fmsmsx154.amr.corp.intel.com (10.18.116.70) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 19 Oct 2018 11:26:13 -0700 Received: from fmsmsx108.amr.corp.intel.com ([169.254.9.237]) by FMSMSX154.amr.corp.intel.com ([169.254.6.126]) with mapi id 14.03.0319.002; Fri, 19 Oct 2018 11:26:13 -0700 From: "Pathak, Pravin" To: "Trahe, Fiona" , "users@dpdk.org" Thread-Topic: Crypto QAT device not found Thread-Index: AdRnKRXD20Lii5N3ToKo7aE94IX7JwAEow1wACdioGA= Date: Fri, 19 Oct 2018 18:26:13 +0000 Message-ID: <168A68C163D584429EF02A476D527442490F685F@FMSMSX108.amr.corp.intel.com> References: <168A68C163D584429EF02A476D527442490F5F60@FMSMSX108.amr.corp.intel.com> <348A99DA5F5B7549AA880327E580B435896503E4@IRSMSX101.ger.corp.intel.com> In-Reply-To: <348A99DA5F5B7549AA880327E580B435896503E4@IRSMSX101.ger.corp.intel.com> Accept-Language: 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: [10.1.200.108] 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 18:26:16 -0000 Hi Fiona - Thanks for the reply. I tried -cdev_type HW but it did not help. I am not= sure of DPDK supports the device on our board. Device is with ID 37c8/c9 3d:00.0 Co-processor: Intel Corporation Device 37c8 (rev 04) 3f:00.0 Co-processor: Intel Corporation Device 37c8 (rev 04) da:00.0 Co-processor: Intel Corporation Device 37c8 (rev 04) 3d:01.0 Co-processor: Intel Corporation Device 37c9 (rev 04) 3d:01.1 Co-processor: Intel Corporation Device 37c9 (rev 04) 3d:01.2 Co-processor: Intel Corporation Device 37c9 (rev 04) 3d:01.3 Co-processor: Intel Corporation Device 37c9 (rev 04) ........ Everything looks correct except DPDK does not see these crypto devices. It = seems virtual device if I add one. Is there any command like argument I need to pass or build option other tha= n CONFIG_RTE_LIBRTE_PMD_QAT=3Dy PFs are bound to Kernel and VFs are bound to DPDK. Crypto devices using kernel 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 0000:3d:00.0 'Device 37c8' if=3D drv=3Dc6xx unused=3Dqat_c62x,igb_uio 0000:3f:00.0 'Device 37c8' if=3D drv=3Dc6xx unused=3Dqat_c62x,igb_uio 0000:da:00.0 'Device 37c8' if=3D drv=3Dc6xx unused=3Dqat_c62x,igb_uio 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 0000:3d:01.1 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf 0000:3d:01.2 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf 0000:3d:01.3 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf 0000:3d:01.4 'Device 37c9' drv=3Digb_uio unused=3Dqat_c62xvf # Drivers loaded pkpathak@paamrpdk03:~/acp/snr/install$ lsmod | grep qat qat_c62xvf 16384 0 qat_c62x 20480 0 intel_qat 163840 3 qat_c62x,qat_c62xvf,usdm_drv uio 20480 2 igb_uio,intel_qat authenc 16384 1 intel_qat Anything you can spot incorrect or missing? Regards Pravin -----Original Message----- From: Trahe, Fiona=20 Sent: Thursday, October 18, 2018 8:05 PM To: Pathak, Pravin ; users@dpdk.org Subject: RE: Crypto QAT device not found Hi Pravin, See below. > -----Original Message----- > From: users [mailto:users-bounces@dpdk.org] On Behalf Of Pathak,=20 > 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=20 > =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=20 > 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 dpdk-test-crypto-perf tool. For that for QAT you s= hould whitelist the device. e.g.: -w 0000:3d:01.0 ( before the -- , i.e. it's an EAL parameter) and use --d= evtype crypto_qat (after the -- , it's a parameter for the application). The terminology of --vdev changed in a recent release, so refer to the vers= ion of 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