From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Meng Wang <meng.w.wang@oracle.com>, "users@dpdk.org" <users@dpdk.org>
Cc: "Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-users] [Crypto-QAT] queue pairs per QAT device
Date: Tue, 14 May 2019 17:04:57 +0000 [thread overview]
Message-ID: <348A99DA5F5B7549AA880327E580B43589767FB3@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <100a5208-2fde-ab32-c8e1-22964acce5fe@oracle.com>
Hi Meng,
> -----Original Message-----
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Meng Wang
> Sent: Monday, May 13, 2019 7:47 PM
> To: users@dpdk.org
> Subject: [dpdk-users] [Crypto-QAT] queue pairs per QAT device
>
> Hi,
>
> I'm trying to understand how queue pairs get setup on QAT. I have
> created one VF for each lcore. From qat code it seems support up to 2
> qps per device/VF, one for each direction. Then I found that each queue
> pair has its own qat_queue rx/tx.
>
> /* Maximum number of qps on a device for any service type */
> #define ADF_MAX_QPS_ON_ANY_SERVICE 2
> #define ADF_RING_DIR_TX 0
> #define ADF_RING_DIR_RX 1
>
> How does the direction of qp correlate to direction of qat_queue? Is one
> queue pair sufficient to transmit packet between QAT and application per
> core?
>
> Thanks,
> Meng
[Fiona] There is no direction associated with a qp - as you noted each queue pair
has both a transmit and a receive queue. (or 2 rings, if you're familiar with other QAT drivers)
So yes, one qp is sufficient and you should enqueue and dequeue to/from the same qp.
prev parent reply other threads:[~2019-05-14 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 18:47 Meng Wang
2019-05-14 17:04 ` Trahe, Fiona [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=348A99DA5F5B7549AA880327E580B43589767FB3@IRSMSX101.ger.corp.intel.com \
--to=fiona.trahe@intel.com \
--cc=meng.w.wang@oracle.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).