From: Zhangfei Gao <zhangfei.gao@linaro.org>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: questions about crypto_scheduler
Date: Fri, 16 Dec 2022 14:54:48 +0800 [thread overview]
Message-ID: <3637a6bf-beee-0994-203c-69c9a77a3042@linaro.org> (raw)
Hi, Akhil
Excuse me for the question.
I am testing UADK crypto performance with dpdk-test-crypto-perf, and
want to use multi-thread or multi-session for better performance, so
trying to use crypto_scheduler.
CMD like
sudo dpdk-test-crypto-perf -l 1,2 --vdev "crypto_uadk0" --vdev
"crypto_uadk1" --vdev
"crypto_scheduler,worker=crypto_uadk0,worker=crypto_uadk1,mode=round-robin"
-- --devtype crypto_scheduler --optype cipher-only --buffer-sz 8192
Though multi-worker is set but found it is just using one worker.
Since uadk_cryptodev_probe gets the same dev->driver_id =
uadk_cryptodev_driver_id in multi-probe.
Then scheduler_pmd_sym_session_configure will treat only one worker,
and call rte_cryptodev_sym_session_create only once.
if (configured_sess[j].driver_id == worker->driver_id)
break
Do I misuse the crypto_scheduler for the multi-thread or multi-session.
Thanks in advance.
next reply other threads:[~2022-12-16 6:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-16 6:54 Zhangfei Gao [this message]
2022-12-16 9:27 ` Zhang, Fan
2022-12-16 10:31 ` [EXT] " Akhil Goyal
2022-12-21 9:19 ` Zhang, Fan
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=3637a6bf-beee-0994-203c-69c9a77a3042@linaro.org \
--to=zhangfei.gao@linaro.org \
--cc=dev@dpdk.org \
--cc=gakhil@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).