From: "Zhang, Fan" <fanzhang.oss@gmail.com>
To: Anoob Joseph <anoobj@marvell.com>,
Akhil Goyal <gakhil@marvell.com>,
Ruifeng Wang <ruifeng.wang@arm.com>,
Gagandeep Singh <g.singh@nxp.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Kai Ji <kai.ji@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
Matan Azrad <matan@nvidia.com>,
Zhangfei Gao <zhangfei.gao@linaro.org>
Cc: Ashwin Sekhar T K <asekhar@marvell.com>,
Jerin Jacob <jerinj@marvell.com>,
dev@dpdk.org
Subject: Re: [PATCH] cryptodev: increase default max nb queue pairs
Date: Wed, 4 Jan 2023 10:58:59 +0000 [thread overview]
Message-ID: <7107cb6f-69e2-808c-6274-583a4484b9ca@gmail.com> (raw)
In-Reply-To: <20230104073021.1039-1-anoobj@marvell.com>
On 1/4/2023 7:30 AM, Anoob Joseph wrote:
> Increase default maximum number of queue pairs to 64. For sw crypto
> PMDs, the number of queue pairs can be increased as required. The
> default value (which is set to 8), prevents usage of sw cryptodev PMDs
> with larger number of cores.
>
> Application would be allowed to specify the number of queue pairs it
> wishes to use. Only the upper bound is changed from 8 to 64.
>
> Allow PMDs such as crypto_armv8 to run on larger number of cores.
>
> Signed-off-by: Anoob Joseph <anoobj@marvell.com>
> ---
> lib/cryptodev/cryptodev_pmd.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/cryptodev/cryptodev_pmd.h b/lib/cryptodev/cryptodev_pmd.h
> index 0020102eb7..913a8f3623 100644
> --- a/lib/cryptodev/cryptodev_pmd.h
> +++ b/lib/cryptodev/cryptodev_pmd.h
> @@ -29,7 +29,7 @@ extern "C" {
> #include "rte_cryptodev.h"
>
>
> -#define RTE_CRYPTODEV_PMD_DEFAULT_MAX_NB_QUEUE_PAIRS 8
> +#define RTE_CRYPTODEV_PMD_DEFAULT_MAX_NB_QUEUE_PAIRS 64
>
> #define RTE_CRYPTODEV_PMD_NAME_ARG ("name")
> #define RTE_CRYPTODEV_PMD_MAX_NB_QP_ARG ("max_nb_queue_pairs")
Acked-by: Fan Zhang <fanzhang.oss@gmail.com>
next prev parent reply other threads:[~2023-01-04 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 7:30 Anoob Joseph
2023-01-04 10:58 ` Zhang, Fan [this message]
2023-01-10 6:41 ` Ruifeng Wang
2023-01-10 7:07 ` Anoob Joseph
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=7107cb6f-69e2-808c-6274-583a4484b9ca@gmail.com \
--to=fanzhang.oss@gmail.com \
--cc=anoobj@marvell.com \
--cc=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=g.singh@nxp.com \
--cc=gakhil@marvell.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=kai.ji@intel.com \
--cc=matan@nvidia.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=ruifeng.wang@arm.com \
--cc=zhangfei.gao@linaro.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).