From: Yu Jiang <yux.jiang@intel.com>
To: varalakshmi.s@intel.com, dts@dpdk.org
Cc: Yu Jiang <yux.jiang@intel.com>
Subject: [dts][PATCH V1 1/2] test_plans/virtio_ipsec_cryptodev_func: rename slave to worker according to dpdk20.11 change
Date: Fri, 14 Apr 2023 13:44:06 +0800 [thread overview]
Message-ID: <20230414054407.1522092-2-yux.jiang@intel.com> (raw)
In-Reply-To: <20230414054407.1522092-1-yux.jiang@intel.com>
According to dpdk20.11 commit id:
28f5375d83 test/crypto: rename slave to worker
85b00824ae crypto/scheduler: rename slave to worker
rename slave to worker.
Signed-off-by: Yu Jiang <yux.jiang@intel.com>
---
test_plans/virtio_ipsec_cryptodev_func_test_plan.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/test_plans/virtio_ipsec_cryptodev_func_test_plan.rst b/test_plans/virtio_ipsec_cryptodev_func_test_plan.rst
index cb390181..d0e109d1 100644
--- a/test_plans/virtio_ipsec_cryptodev_func_test_plan.rst
+++ b/test_plans/virtio_ipsec_cryptodev_func_test_plan.rst
@@ -101,7 +101,7 @@ In Host:
./x86_64-native-linuxapp-gcc/examples/dpdk-vhost_crypto \
--socket-mem 2048,0 --legacy-mem \
-a 1a:01.0 -a 1c:01.0 -a 1e:01.0 \
- --vdev crypto_scheduler_pmd_1,slave=0000:1a:01.0_qat_sym,slave=0000:1c:01.0_qat_sym,slave=0000:1e:01.0_qat_sym,mode=round-robin,ordering=enable \
+ --vdev crypto_scheduler_pmd_1,worker=0000:1a:01.0_qat_sym,worker=0000:1c:01.0_qat_sym,worker=0000:1e:01.0_qat_sym,mode=round-robin,ordering=enable \
-l 8,9,10,11,12 -n 6 \
-- --config "(9,0,0),(10,0,0),(11,0,0),(12,0,0)" \
--socket-file 9,/tmp/vm0_crypto0.sock \
--
2.25.1
next prev parent reply other threads:[~2023-04-14 5:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 5:44 [dts][PATCH V1 0/2] " Yu Jiang
2023-04-14 5:44 ` Yu Jiang [this message]
2023-04-14 5:44 ` [dts][PATCH V1 2/2] tests/l2fwd_cryptodev_func: " Yu Jiang
2023-04-14 8:47 ` S, Varalakshmi
2023-04-23 8:54 ` lijuan.tu
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=20230414054407.1522092-2-yux.jiang@intel.com \
--to=yux.jiang@intel.com \
--cc=dts@dpdk.org \
--cc=varalakshmi.s@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).