[dpdk-users] [dpdk-dev] Query for QAT software running in SR-IOV mode at VM

Trahe, Fiona fiona.trahe at intel.com
Mon Mar 27 19:14:47 CEST 2017


Hi Pankaj,
See below

> -----Original Message-----
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Pankaj Joshi
> Sent: Monday, March 27, 2017 5:20 PM
> To: qat-linux <qat-linux at intel.com>; dev at dpdk.org; users at dpdk.org
> Subject: [dpdk-dev] Query for QAT software running in SR-IOV mode at VM
> 
> Hello Team,
> 
> I have followed the steps given in section 10.4 in below link :
> 
> 
> 
> http://dpdk.org/doc/guides/cryptodevs/qat.html
> 
> 
> <http://dpdk.org/doc/guides/cryptodevs/qat.html>
> 
> 
> <http://dpdk.org/doc/guides/cryptodevs/qat.html>
> 
> <http://dpdk.org/doc/guides/cryptodevs/qat.html>
> 
> 1.          Export ICP_WITHOUT_IOMMU=1, and install the QAT software in
> host ( SR-IOV mode ).
> 
> 2.         Checked that there are 32 VF devices are there.
> 
> 3.        Launched VM and add 1 PCI device to the VM.
> 
> 4.       1 device map to 1 /etc/dh895xcc_qa_dev0.conf file which is having
> 2 instance.
> 
> 5.        Install QAT software in VM m/c with guest mode as explained in
> below link.
> 
> 6.    Running my application, it is able to submit the request to hardware
> queue using API,cpaCySymDpEnqueueOp.
> 
> 7.     But unable to call the registered callback function.
> 
> http://www.intel.com/content/dam/www/public/us/en/documents/applicati
> on-notes/virtualization-technology-with-quickassist-technology-app-note.pdf
> 
> How I can debug the issue, or how I enable the logs in QAT software.
> 
If you're trying to use QAT with DPDK cryptodev API then there's no need for steps 4,5,6,7
above. These are steps for using the QA API, i.e. cpaCyXXX APIs.

Also the ICP_WITHOUT_IOMMU condition is only needed if intending to access the QAT HW from 
the Host. If you intend to access the crypto services on QAT via the VF on a VM, then you can 
use the standard out of the box install for a HOST.

Once the VF device is passed through to the VM, on the VM it can be passed straight through 
to the user-space DPDK QAT PMD without a QAT kernel driver.
i.e. follow the bind commands on http://dpdk.org/doc/guides/cryptodevs/qat.html
to bind the VF to either igb_uio or vfio-pci

Then build your application to use the cryptodev APIs, see 
http://dpdk.org/doc/guides/sample_app_ug/ipsec_secgw.html
for an example of how to do this.
If you just want to get it up and running without a traffic generator, you can use the test app to 
run a sanity check against any of the crypto poll mode drivers, e.g. to run some basic functional tests
against the QAT PMD, e.g.
use dpdk/usertools/dpdk-setup.sh to allocate huge pages
start test app, e.g. test -n1 -l1  
(The test app has moved in a recent release, you should find it at either dpdk/build/app/ or dpdk/build/build/test/test ) 
Run the qat test suite with 
>cryptodev_qat_autotest


> Please help here.
> 
> Regards,
> 
> Pankaj Joshi


More information about the users mailing list