From: Yaqi Tang <yaqi.tang@intel.com>
To: dts@dpdk.org
Cc: Yaqi Tang <yaqi.tang@intel.com>
Subject: [dts][PATCH V1] test_plans/short_live: modify testpmd config param
Date: Wed, 8 Jun 2022 04:50:29 +0000 [thread overview]
Message-ID: <20220608045029.350571-2-yaqi.tang@intel.com> (raw)
In-Reply-To: <20220608045029.350571-1-yaqi.tang@intel.com>
The tetspmd config param of the test plan is not match that of the test script, so modify test plan testpmd config param.
And adjust the format of test plan according to test plan template.
Signed-off-by: Yaqi Tang <yaqi.tang@intel.com>
---
test_plans/short_live_test_plan.rst | 85 +++++++++++++++++------------
1 file changed, 49 insertions(+), 36 deletions(-)
diff --git a/test_plans/short_live_test_plan.rst b/test_plans/short_live_test_plan.rst
index 2f6c9cb1..e72287a0 100644
--- a/test_plans/short_live_test_plan.rst
+++ b/test_plans/short_live_test_plan.rst
@@ -5,11 +5,13 @@
Short-lived Application Tests
=============================
+Description
+===========
This feature is to reduce application start-up time, and do more
cleanup when exit so that it could rerun many times.
Prerequisites
--------------
+=============
To test this feature, need to use linux time and start testpmd by: create
and mount hugepage, must create more hugepages so that could measure time more
@@ -27,16 +29,18 @@ Start testpmd using time::
# echo quit | time ./app/dpdk-testpmd -c 0x3 -n 4 -- -i
-Test Case 1: basic fwd testing
+Test Case 1: Basic fwd testing
------------------------------
1. Start testpmd::
./app/dpdk-testpmd -c 0x3 -n 4 -- -i
-2. Set fwd mac
-3. Send packet from pkg
-4. Check all packets could be fwd back
+2. Set fwd mac.
+
+3. Send packet from pkg.
+
+4. Check all packets could be fwd back.
Test Case 2: Get start up time
------------------------------
@@ -45,8 +49,9 @@ Test Case 2: Get start up time
echo quit | time ./app/dpdk-testpmd -c 0x3 -n 4 --huge-dir /mnt/huge -- -i
-2. Get the time stats of the startup
-3. Repeat step 1~2 for at least 5 times to get the average
+2. Get the time stats of the startup.
+
+3. Repeat step 1~2 for at least 5 times to get the average.
Test Case 3: Clean up with Signal -- testpmd
--------------------------------------------
@@ -58,69 +63,77 @@ Test Case 3: Clean up with Signal -- testpmd
2. Start testpmd::
- ./app/dpdk-testpmd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -i
+ ./app/dpdk-testpmd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -i --portmask=0x3
+
+3. Set fwd mac.
+
+4. Send packets from pkg.
+
+5. Check all packets could be fwd back.
-3. Set fwd mac
-4. Send packets from pkg
-5. Check all packets could be fwd back
6. Kill the testpmd in shell using below commands alternately::
- SIGINT: pkill -2 dpdk-testpmd
- SIGTERM: pkill -15 dpdk-testpmd
+ SIGINT: pkill -2 dpdk-testpmd
+ SIGTERM: pkill -15 dpdk-testpmd
7. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
-
Test Case 4: Clean up with Signal -- l2fwd
------------------------------------------
-0. Build l2fwd example::
+1. Build l2fwd example::
meson configure -Dexamples=l2fwd x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
-1. Create 4G hugepages, so that could save times when repeat::
+2. Create 4G hugepages, so that could save times when repeat::
echo 2048 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
mount -t hugetlbfs hugetlbfs /mnt/huge1
-2. Start testpmd::
+3. Start testpmd::
- ./examples/dpdk-l2fwd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -p 0x01
+ ./examples/dpdk-l2fwd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -p 0x03
-3. Set fwd mac
-4. Send packets from pkg
-5. Check all packets could be fwd back
-6. Kill the testpmd in shell using below commands alternately::
+4. Set fwd mac.
- SIGINT: pkill -2 dpdk-l2fwd
- SIGTERM: pkill -15 dpdk-l2fwd
+5. Send packets from pkg.
-7. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
+6. Check all packets could be fwd back.
+
+7. Kill the testpmd in shell using below commands alternately::
+
+ SIGINT: pkill -2 dpdk-l2fwd
+ SIGTERM: pkill -15 dpdk-l2fwd
+
+8. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
Test Case 5: Clean up with Signal -- l3fwd
------------------------------------------
-0. Build l3fwd example::
+1. Build l3fwd example::
meson configure -Dexamples=l3fwd x86_64-native-linuxapp-gcc
ninja -C x86_64-native-linuxapp-gcc
-1. Create 4G hugepages, so that could save times when repeat::
+2. Create 4G hugepages, so that could save times when repeat::
echo 2048 > /sys/kernel/mm/hugepages/hugepages-2048kB/nr_hugepages
mount -t hugetlbfs hugetlbfs /mnt/huge1
-2. Start testpmd::
+3. Start testpmd::
- ./examples/dpdk-l3fwd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -p 0x01 --config="(0,0,1)"
+ ./examples/dpdk-l3fwd -c 0x3 -n 4 --huge-dir /mnt/huge1 -- -p 0x03 --config='(0,0,1),(1,0,2)' &
-3. Set fwd mac
-4. Send packets from pkg
-5. Check all packets could be fwd back
-6. Kill the testpmd in shell using below commands alternately::
+4. Set fwd mac.
- SIGINT: pkill -2 dpdk-l3fwd
- SIGTERM: pkill -15 dpdk-l3fwd
+5. Send packets from pkg.
-7. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
+6. Check all packets could be fwd back.
+
+7. Kill the testpmd in shell using below commands alternately::
+
+ SIGINT: pkill -2 dpdk-l3fwd
+ SIGTERM: pkill -15 dpdk-l3fwd
+
+8. Repeat step 1-6 for 20 times, and packet must be fwd back with no error for each time.
--
2.25.1
next prev parent reply other threads:[~2022-06-08 4:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-08 4:50 [dts][PATCH V1] test_plans/runtime_vf_queue_number: adjust test plan format Yaqi Tang
2022-06-08 4:50 ` Yaqi Tang [this message]
2022-06-15 9:04 ` [dts][PATCH V1] test_plans/short_live: modify testpmd config param lijuan.tu
2022-06-15 9:05 ` [dts][PATCH V1] test_plans/runtime_vf_queue_number: adjust test plan format 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=20220608045029.350571-2-yaqi.tang@intel.com \
--to=yaqi.tang@intel.com \
--cc=dts@dpdk.org \
/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).