[dpdk-users] Crypto QAT device not found

Trahe, Fiona fiona.trahe at intel.com
Fri Oct 19 02:05:14 CEST 2018


Hi Pravin,
See below.

> -----Original Message-----
> From: users [mailto:users-bounces at dpdk.org] On Behalf Of Pathak, Pravin
> Sent: Thursday, October 18, 2018 2:30 PM
> To: users at dpdk.org
> Subject: [dpdk-users] Crypto QAT device not found
> 
> 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
> ===========================================
> 0000:3d:01.0 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:01.1 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:01.2 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:01.3 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:01.4 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:01.5 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:01.6 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:01.7 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:02.0 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:02.1 'Device 37c9' drv=igb_uio unused=qat_c62xvf,vfio-pci
> 0000:3d:02.2 'Device 37c9' drv=igb_uio unused=qat_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 able to use HW device.
> Your help is appreciated.
> 
> 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 should whitelist the device. e.g.:
 -w 0000:3d:01.0 ( before the -- , i.e. it's an EAL parameter) 
and  use --devtype crypto_qat  (after the -- , it's a parameter for the application).
The terminology of --vdev changed in a recent release, so refer to the version 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



More information about the users mailing list