From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: "Pathak, Pravin" <pravin.pathak@intel.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Crypto QAT device not found
Date: Fri, 19 Oct 2018 00:05:14 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B435896503E4@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <168A68C163D584429EF02A476D527442490F5F60@FMSMSX108.amr.corp.intel.com>
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
>
> 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
next prev parent reply other threads:[~2018-10-19 0:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 21:30 Pathak, Pravin
2018-10-19 0:05 ` Trahe, Fiona [this message]
2018-10-19 18:26 ` Pathak, Pravin
2018-10-19 20:25 ` Trahe, Fiona
2018-10-19 21:00 ` Pathak, Pravin
2018-10-19 21:40 ` Trahe, Fiona
2018-10-19 22:01 ` Pathak, Pravin
2018-10-19 23:06 ` Wiles, Keith
2018-10-23 1:20 ` Pathak, Pravin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=348A99DA5F5B7549AA880327E580B435896503E4@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=pravin.pathak@intel.com \
--cc=users@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).