From: Ciara Power <ciara.power@intel.com>
To: dev@dpdk.org
Cc: kai.ji@intel.com, Ciara Power <ciara.power@intel.com>,
Kevin O'Sullivan <kevin.osullivan@intel.com>
Subject: [PATCH 1/2] test/crypto-perf: fix number of sessions for cores
Date: Mon, 14 Nov 2022 16:57:47 +0000 [thread overview]
Message-ID: <20221114165748.307086-1-ciara.power@intel.com> (raw)
Currently the performance application creates a device session per lcore.
This was not reflected in how many session objects were available
in the mempool, when using a scheduler device.
The number of lcores is now taken into consideration when calculating
how many sessions are needed for the scheduler.
Fixes: 09fcf99dcad2 ("test/crypto-perf: fix number of scheduler sessions")
Reported-by: Kevin O'Sullivan <kevin.osullivan@intel.com>
Signed-off-by: Ciara Power <ciara.power@intel.com>
---
app/test-crypto-perf/main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/app/test-crypto-perf/main.c b/app/test-crypto-perf/main.c
index 0fe47c6caa..22f6b2b3ba 100644
--- a/app/test-crypto-perf/main.c
+++ b/app/test-crypto-perf/main.c
@@ -269,8 +269,8 @@ cperf_initialize_cryptodev(struct cperf_options *opts, uint8_t *enabled_cdevs)
uint32_t nb_slaves =
rte_cryptodev_scheduler_workers_get(cdev_id,
NULL);
- /* scheduler session header + 1 session per worker qp */
- sessions_needed = 1 + enabled_cdev_count *
+ /* scheduler session header per lcore + 1 session per worker qp */
+ sessions_needed = nb_lcores + enabled_cdev_count *
opts->nb_qps * nb_slaves;
#endif
} else
--
2.34.1
next reply other threads:[~2022-11-14 16:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 16:57 Ciara Power [this message]
2022-11-14 16:57 ` [PATCH 2/2] test/crypto-perf: replace slave with worker Ciara Power
2022-11-15 9:30 ` [EXT] [PATCH 1/2] test/crypto-perf: fix number of sessions for cores Akhil Goyal
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=20221114165748.307086-1-ciara.power@intel.com \
--to=ciara.power@intel.com \
--cc=dev@dpdk.org \
--cc=kai.ji@intel.com \
--cc=kevin.osullivan@intel.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).