From: Chinmaya Dwibedy <ckdwibedy@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Maximum number of queue pairs per QAT device (using dpdk-2.2.0)
Date: Thu, 29 Dec 2016 18:42:37 +0530 [thread overview]
Message-ID: <CAMHS8REx29sGY1BkOPA0m4Gb45314qo4Kx1Gz+XpFWb7Wj00Kw@mail.gmail.com> (raw)
Hi,
I am using the dpdk-2.2.0. I find the maximum number of queue pairs
supported by the AESNI device is equal to value of
CONFIG_RTE_AESNI_MB_PMD_MAX_NB_QUEUE_PAIRS (in
dpdk-2.2.0/config/common_linuxapp). I have created a mapping between
logical core ID and crypto device index. Also want to keep one queue per
IPsec security association (Inbound or Outbound). With this, even same core
and crypto device processes the packet of two security association (One is
inbound and another is outbound) without intermixing.
I find the max_nb_queue_pairs to be 2 (via rte_cryptodev_info_get () for
QAT device. Is there any configuration to increase the maximum number of
queue pairs per QAT device? If not , how can I use/support multiple queues
per QAT device ? Please suggest.
Note that, I have assigned 16 VFs to VM (Openstack).
Regards,
Chinmaya
next reply other threads:[~2016-12-29 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 13:12 Chinmaya Dwibedy [this message]
2017-01-03 5:54 ` Chinmaya Dwibedy
2017-01-03 11:06 ` Trahe, Fiona
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=CAMHS8REx29sGY1BkOPA0m4Gb45314qo4Kx1Gz+XpFWb7Wj00Kw@mail.gmail.com \
--to=ckdwibedy@gmail.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).