From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 104A45F33 for ; Thu, 18 Oct 2018 23:30:18 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga006.fm.intel.com ([10.253.24.20]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 Oct 2018 14:30:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,397,1534834800"; d="scan'208,217";a="273644170" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by fmsmga006.fm.intel.com with ESMTP; 18 Oct 2018 14:30:17 -0700 Received: from fmsmsx114.amr.corp.intel.com (10.18.116.8) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 18 Oct 2018 14:30:17 -0700 Received: from fmsmsx108.amr.corp.intel.com ([169.254.9.237]) by FMSMSX114.amr.corp.intel.com ([169.254.6.177]) with mapi id 14.03.0319.002; Thu, 18 Oct 2018 14:30:17 -0700 From: "Pathak, Pravin" To: "users@dpdk.org" Thread-Topic: Crypto QAT device not found Thread-Index: AdRnKRXD20Lii5N3ToKo7aE94IX7Jw== Date: Thu, 18 Oct 2018 21:30:16 +0000 Message-ID: <168A68C163D584429EF02A476D527442490F5F60@FMSMSX108.amr.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.107] 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: [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: Thu, 18 Oct 2018 21:30:19 -0000 Hi All - I have server with Intel QAT c62x device. I followed all documentation. - Rebuild DPDK to use QAT - QAT drivers are loaded. - QAT devices are bound to DPDK 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 But if I use l2fwd-crypto sample, I get no crypto device found error 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 It works if I add virtual device --vdev "crypto_aesni_mb0" but I am not ab= le to use HW device. Your help is appreciated. Thanks Pravin