DPDK usage discussions
 help / color / mirror / Atom feed
From: "Kusztal, ArkadiuszX" <arkadiuszx.kusztal@intel.com>
To: "Anjum, Sohail" <sohail.eic06g@nctu.edu.tw>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] qat is not working with dpdk
Date: Thu, 4 Mar 2021 07:38:03 +0000	[thread overview]
Message-ID: <CY4PR11MB18303ED7EC744A62EB7548F39F979@CY4PR11MB1830.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CABsxamgiEyAK4r40hNC33J_qPuwpXSaopPNHcnkyXB6Z4jFzVA@mail.gmail.com>

> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of Anjum, Sohail
> Sent: Thursday, March 4, 2021 7:15 AM
> To: users@dpdk.org
> Subject: Re: [dpdk-users] qat is not working with dpdk
> 
> Hello everyone I am trying to run dpdk-test-crypto-perf with sha1-hmac and
> sha2-256-hamc.
> 
> But whenever I run this command
> {./x86_64-native-linuxapp-gcc/build/app/test-crypto-perf/dpdk-test-cryptoperf
> --socket-mem 2048,0 --legacy-mem -w 0000:02:01.0 -w 0000:02:01.1 -w
> 0000:02:01.2 -w 0000:02:01.3 -l 4,5,13,6,14 -n 4 -- --buffer-sz
> 64,128,256,512,1024,2048 --optype cipher-then-auth --ptest throughput -auth-
> key-sz 64 --cipher-key-sz 16 --devtype* crypto_qat* --cipher-iv-sz 16
> -
> -auth-op generate --burst-sz 32 --total-ops 30000000 --silent --digest-sz
> 20 --auth-algo sha1-hmac --cipher-algo aes-cbc --cipher-op encrypt }  I get this
> error message()USER1 Failed to initialise requested crypto device type)  and I
> don't know how to solve this problem. Need your suggestions. I don't have any
> idea how to initialise a crypto device.
> However I already have qat installed in my Pc and service is in the start mode.
> 
> On Thu, Mar 4, 2021 at 2:11 PM Anjum, Sohail <sohail.eic06g@nctu.edu.tw>
> wrote:
> 
> >
> > Hello everyone I am trying to run dpdk-test-crypto-perf with sha1-hmac
> > and sha2-256-hamc.
> >
> > But whenever I run this command I get this error message and I don't
> > know how to solve this problem. Need your suggestions. I don't have
> > any idea how to initialise a crypto device. However I already have qat
> > installed in my Pc and service is in the start mode.

Are all devices you have specified bound to vfio-pci (eventually igb-uio) according to "Bind to the vfio-pci driver" section in
Doc/guides/cryptodevs/qat.rst?

Do you see any additional informations like:
"Number of needed queue pairs is higher than the maximum number of queue pairs per device."
Or
"No crypto devices type crypto_qat available"?
It is usually shown over this line:
"# Crypto Performance Application Options:'"

> >
> > --
> > *Regards*,
> >
> > *Sohail Anjum*
> >
> > *EECS Department.*
> > *National Chiao Tung University, Hsinchu, Taiwan*
> >
> >
> 
> --
> *Regards*,
> 
> *Sohail Anjum*
> 
> *EECS Department.*
> *National Chiao Tung University, Hsinchu, Taiwan*

      reply	other threads:[~2021-03-04  7:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  6:11 Anjum, Sohail
2021-03-04  6:14 ` Anjum, Sohail
2021-03-04  7:38   ` Kusztal, ArkadiuszX [this message]

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=CY4PR11MB18303ED7EC744A62EB7548F39F979@CY4PR11MB1830.namprd11.prod.outlook.com \
    --to=arkadiuszx.kusztal@intel.com \
    --cc=sohail.eic06g@nctu.edu.tw \
    --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).