From: Yu Jiang <yux.jiang@intel.com>
To: lijuan.tu@intel.com, dts@dpdk.org
Cc: Yu Jiang <yux.jiang@intel.com>
Subject: [dts][PATCH V1 2/3] test_plans/l2fwd_cryptodev_func&inline_ipsec: modify test plan to adapt meson build
Date: Thu, 14 Apr 2022 14:05:48 +0000 [thread overview]
Message-ID: <20220414140549.1579777-3-yux.jiang@intel.com> (raw)
In-Reply-To: <20220414140549.1579777-1-yux.jiang@intel.com>
test_plans/l2fwd_cryptodev_func&inline_ipsec: modify test plan to adapt meson build
Signed-off-by: Yu Jiang <yux.jiang@intel.com>
---
test_plans/inline_ipsec_test_plan.rst | 20 +++++++++----------
test_plans/l2fwd_cryptodev_func_test_plan.rst | 2 +-
2 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/test_plans/inline_ipsec_test_plan.rst b/test_plans/inline_ipsec_test_plan.rst
index f3b0a8cc..0b4e45a1 100644
--- a/test_plans/inline_ipsec_test_plan.rst
+++ b/test_plans/inline_ipsec_test_plan.rst
@@ -145,7 +145,7 @@ Test Case: IPSec Encryption
===========================
Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 --config="(0,0,20),(1,0,21)" -f ./enc.cfg
@@ -195,7 +195,7 @@ Test Case: IPSec Encryption with Jumboframe
===========================================
Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 --config="(0,0,20),(1,0,21)" -f ./enc.cfg
@@ -215,7 +215,7 @@ Check burst esp packets can't be received from unprotected port.
Set jumbo frames size as 9000, start it with port 1 assigned to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 -j 9000 --config="(0,0,20),(1,0,21)" -f ./enc.cfg
@@ -240,7 +240,7 @@ Create configuration file with multiple SP/SA/RT rules for different ip address.
Start ipsec-secgw with two queues enabled on each port and port 1 assigned to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 --config="(0,0,20),(0,1,20),(1,0,21),(1,1,21)" -f ./enc_rss.cfg
@@ -260,7 +260,7 @@ Test Case: IPSec Decryption
===========================
Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 --config="(0,0,20),(1,0,21)" -f ./dec.cfg
@@ -276,7 +276,7 @@ Test Case: IPSec Decryption with wrong key
==========================================
Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 --config="(0,0,20),(1,0,21)" -f ./dec.cfg
@@ -296,7 +296,7 @@ IPsec application will produce error "IPSEC_ESP: failed crypto op".
Test Case: IPSec Decryption with Jumboframe
===========================================
Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 --config="(0,0,20),(1,0,21)" -f ./dec.cfg
@@ -313,7 +313,7 @@ Check burst(8192) packets which have been decapsulated can't be received from pr
Set jumbo frames size as 9000, start it with port 1 assigned to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 -j 9000 --config="(0,0,20),(1,0,21)" -f ./dec.cfg
@@ -335,7 +335,7 @@ Create configuration file with multiple SA rule for different ip address.
Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1 --vdev
"crypto_null" --log-level 8 --socket-mem 1024,1 -- -p 0xf -P -u
0x2 -config="(0,0,20),(0,1,20),(1,0,21),(1,1,21)" -f ./dec_rss.cfg
@@ -352,7 +352,7 @@ Test Case: IPSec Encryption/Decryption simultaneously
=====================================================
Start ipsec-secgw with two 82599 ports and assign port 1 to unprotected mode::
- sudo ./build/ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1
+ sudo ./x86_64-default-linuxapp-gcc/examples/dpdk-ipsec-secgw -l 20,21 -a 83:00.0 -a 83:00.1
--vdev "crypto_null" --log-level 8 --socket-mem 1024,1
-- -p 0xf -P -u 0x2 --config="(0,0,20),(1,0,21)" -f ./enc_dec.cfg
diff --git a/test_plans/l2fwd_cryptodev_func_test_plan.rst b/test_plans/l2fwd_cryptodev_func_test_plan.rst
index 9ace53d0..889b3fd2 100644
--- a/test_plans/l2fwd_cryptodev_func_test_plan.rst
+++ b/test_plans/l2fwd_cryptodev_func_test_plan.rst
@@ -279,7 +279,7 @@ To test CryptoDev API, an example l2fwd-crypto is added into DPDK.
The test commands of l2fwd-crypto is below::
- ./build/l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD] /
+ ./build/examples/dpdk-l2fwd-crypto [EAL options] -- [-p PORTMASK] [-q NQ] [-s] [-T PERIOD] /
[--cdev_type HW/SW/ANY] [--chain HASH_CIPHER/CIPHER_HASH/CIPHER_ONLY/HASH_ONLY/AEAD] /
[--cipher_algo ALGO] [--cipher_op ENCRYPT/DECRYPT] [--cipher_key KEY] /
[--cipher_key_random_size SIZE] [--cipher_iv IV] [--cipher_iv_random_size SIZE] /
--
2.25.1
next prev parent reply other threads:[~2022-04-14 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 14:05 [dts][PATCH V1 0/3] test_plans/*: " Yu Jiang
2022-04-14 14:05 ` [dts][PATCH V1 1/3] test_plans/vf_interrupt_pmd&sriov_kvm: " Yu Jiang
2022-04-20 3:34 ` lijuan.tu
2022-04-14 14:05 ` Yu Jiang [this message]
2022-04-14 14:05 ` [dts][PATCH V1 3/3] test_plans/external_mempool_handler: " Yu Jiang
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=20220414140549.1579777-3-yux.jiang@intel.com \
--to=yux.jiang@intel.com \
--cc=dts@dpdk.org \
--cc=lijuan.tu@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).