DPDK usage discussions
 help / color / mirror / Atom feed
From: "Joshi, Venkatesh" <venkatesh.joshi@hpe.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: [dpdk-users] QAT VFs using cryptodev - memory requirements
Date: Thu, 3 Dec 2020 12:57:37 +0000	[thread overview]
Message-ID: <AT5PR8401MB1027F4D7911B8AAD5F09DBE2ECF20@AT5PR8401MB1027.NAMPRD84.PROD.OUTLOOK.COM> (raw)

Hi,

I have a DPDK application running 5 instances on 5 CPUs. I have bound 1 QAT VF to each of the CPUs using cryptodev.

I have allocated only a single instance of the following:
* The crypto op pool using rte_crypto_op_pool_create()
* The symmetric session pool using rte_cryptodev_sym_session_pool_create()

So, the pools will be shared by the 5 cryptodevs. Is this safe to do?

Is there any recommendation on whether each cryptodev instance should have its own memory pools?


Regards,
Venkatesh


                 reply	other threads:[~2020-12-03 12:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AT5PR8401MB1027F4D7911B8AAD5F09DBE2ECF20@AT5PR8401MB1027.NAMPRD84.PROD.OUTLOOK.COM \
    --to=venkatesh.joshi@hpe.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).