From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: users@dpdk.org
Subject: Re: [dpdk-users] Issue with ipsec-secgw sample application on VM using Intel QAT device (pass-through mode)
Date: Wed, 15 Jun 2016 13:35:17 +0100 [thread overview]
Message-ID: <ee2ca80f-b202-55fd-07d3-fd7ef4c6759e@intel.com> (raw)
In-Reply-To: <CAMHS8RGXRCNPqpEpbQ68Fm5oLmTFU=wbR2mhmbtaRp=W4a6ETg@mail.gmail.com>
On 15/06/2016 13:01, Chinmaya Dwibedy wrote:
> Also the output lspci on VM as follows
>
> [root@vpn-c openssl-async]# lspci -nn | grep 0435
>
> 00:05.0 Co-processor [0b40]: Intel Corporation Coleto Creek PCIe Endpoint
> [8086:0435]
>
This is the PF, not the VF.
> I run the ipsec-secgw sample application (
> http://dpdk.org/browse/dpdk/tree/examples/ipsec-secgw) on VM with -cdev QAT
> (e.g., #./examples/ipsec-secgw/build/ipsec-secgw -l 0,1 -n 4 -- -p 0x3 -P
> --config="(0,0,0), (1,0,1)" --cdev QAT --ep0) . I found that,
> rte_cryptodev_count_devtype() returns zero (i.e., no QAT crypto device
> found).
>
>
> Can anyone please suggest what might be the issue and the way to resolve
> this ? Also kindly let me know using QAT device (passed through mode) by
> DPDK application is possible or not. Thank you in advance for your time and
> help. please feel free to let me know if additional information is needed.
>
I reckon that your issue is that you are trying to use the PF (not
supported by DPDK)
instead of the VF.
From
http://dpdk.readthedocs.io/en/v2.2.0/cryptodevs/qat.html#installation-using-01-org-qat-driver:
"You can use|cat/proc/icp_dh895xcc_dev0/version|to confirm the driver is
correctly installed.
You can use|lspci-d:443|to confirm the bdf of the 32 VF devices are
available per|DH895xCC|device."
You should pass-through one of the VFs.
Sergio
next prev parent reply other threads:[~2016-06-15 12:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 12:01 Chinmaya Dwibedy
2016-06-15 12:35 ` Sergio Gonzalez Monroy [this message]
2016-06-20 7:33 ` Chinmaya Dwibedy
2016-06-20 8:06 ` Sergio Gonzalez Monroy
2016-06-20 9:08 ` Chinmaya Dwibedy
2016-06-20 9:34 ` Sergio Gonzalez Monroy
2016-06-21 7:26 ` Chinmaya Dwibedy
2016-06-21 15:40 ` Sergio Gonzalez Monroy
2016-06-22 8:09 ` Chinmaya Dwibedy
2016-06-23 11:48 ` Chinmaya Dwibedy
2016-06-24 9:34 ` Chinmaya Dwibedy
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=ee2ca80f-b202-55fd-07d3-fd7ef4c6759e@intel.com \
--to=sergio.gonzalez.monroy@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).