DPDK patches and discussions
 help / color / mirror / Atom feed
From: Volodymyr Fialko <vfialko@marvell.com>
To: <dev@dpdk.org>, Jerin Jacob <jerinj@marvell.com>
Cc: <anoobj@marvell.com>, Volodymyr Fialko <vfialko@marvell.com>
Subject: [PATCH 2/2] app/eventdev: increase number of qp descriptors
Date: Fri, 17 Jun 2022 12:02:17 +0200	[thread overview]
Message-ID: <20220617100217.3356870-3-vfialko@marvell.com> (raw)
In-Reply-To: <20220617100217.3356870-1-vfialko@marvell.com>

Increase number of cryptodev queue pair descriptors by default.

Signed-off-by: Volodymyr Fialko <vfialko@marvell.com>
---
 app/test-eventdev/test_perf_common.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/app/test-eventdev/test_perf_common.c b/app/test-eventdev/test_perf_common.c
index a5e031873d..81420be73a 100644
--- a/app/test-eventdev/test_perf_common.c
+++ b/app/test-eventdev/test_perf_common.c
@@ -6,7 +6,7 @@
 
 #include "test_perf_common.h"
 
-#define NB_CRYPTODEV_DESCRIPTORS 128
+#define NB_CRYPTODEV_DESCRIPTORS 1024
 #define DATA_SIZE		512
 struct modex_test_data {
 	enum rte_crypto_asym_xform_type xform_type;
-- 
2.25.1


  parent reply	other threads:[~2022-06-17 10:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 10:02 [PATCH 0/2] app/eventdev: fix issues with cop alloc and qp size Volodymyr Fialko
2022-06-17 10:02 ` [PATCH 1/2] app/eventdev: add null checks for cop allocations Volodymyr Fialko
2022-06-17 12:06   ` Jerin Jacob
2022-06-17 10:02 ` Volodymyr Fialko [this message]
2022-06-17 12:04   ` [PATCH 2/2] app/eventdev: increase number of qp descriptors Jerin Jacob

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=20220617100217.3356870-3-vfialko@marvell.com \
    --to=vfialko@marvell.com \
    --cc=anoobj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    /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).