From: Wei Ling <weix.ling@intel.com>
To: dts@dpdk.org
Cc: Wei Ling <weix.ling@intel.com>
Subject: [dts][PATCH V1 2/5] test_plans/vhost_user_interrupt_test_plan: migrate CBDMA related testcase to new testsuite
Date: Thu, 19 May 2022 04:13:53 -0400 [thread overview]
Message-ID: <20220519081353.2816053-1-weix.ling@intel.com> (raw)
Migrate CBDMA related testcase to new testsuite.
Signed-off-by: Wei Ling <weix.ling@intel.com>
---
test_plans/vhost_user_interrupt_test_plan.rst | 42 -------------------
1 file changed, 42 deletions(-)
diff --git a/test_plans/vhost_user_interrupt_test_plan.rst b/test_plans/vhost_user_interrupt_test_plan.rst
index fd9394c3..cb2dae75 100644
--- a/test_plans/vhost_user_interrupt_test_plan.rst
+++ b/test_plans/vhost_user_interrupt_test_plan.rst
@@ -127,45 +127,3 @@ Test Case4: Wake up packed ring vhost-user cores with l3fwd-power sample when m
testpmd>start
4. Stop and restart testpmd again, check vhost-user cores will sleep and wakeup again.
-
-Test Case5: Wake up split ring vhost-user cores with l3fwd-power sample when multi queues and cbdma are enabled
-===============================================================================================================
-
-1. Launch virtio-user with server mode::
-
- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-5 -n 4 --no-pci --file-prefix=virtio \
- --vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1,queues=4 -- -i --rxq=4 --txq=4 --rss-ip
-
-2. Bind 4 cbdma ports to vfio-pci driver, then launch l3fwd-power with a virtual vhost device::
-
- ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 9-12 -n 4 --log-level=9 \
- --vdev 'eth_vhost0,iface=/tmp/sock0,queues=4,client=1,dmas=[txq0@80:04.0;txq1@80:04.1;txq2@80:04.2;txq3@80:04.3]' -- -p 0x1 --parse-ptype 1 \
- --config "(0,0,9),(0,1,10),(0,2,11),(0,3,12)"
-
-3. Send packet by testpmd, check vhost-user multi-cores will keep wakeup status::
-
- testpmd>set fwd txonly
- testpmd>start
-
-4. Stop and restart testpmd again, check vhost-user cores will sleep and wakeup again.
-
-Test Case6: Wake up packed ring vhost-user cores with l3fwd-power sample when multi queues and cbdma are enabled
-================================================================================================================
-
-1. Launch virtio-user with server mode::
-
- ./x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l 1-5 -n 4 --no-pci --file-prefix=virtio \
- --vdev=net_virtio_user0,mac=00:11:22:33:44:10,path=/tmp/sock0,server=1,queues=4,packed_vq=1 -- -i --rxq=4 --txq=4 --rss-ip
-
-2. Bind 4 cbdma ports to vfio-pci driver, then launch l3fwd-power with a virtual vhost device::
-
- ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 9-12 -n 4 --log-level=9 \
- --vdev 'eth_vhost0,iface=/tmp/sock0,queues=4,client=1,dmas=[txq0@80:04.0;txq1@80:04.1;txq2@80:04.2;txq3@80:04.3]' -- -p 0x1 --parse-ptype 1 \
- --config "(0,0,9),(0,1,10),(0,2,11),(0,3,12)"
-
-3. Send packet by testpmd, check vhost-user multi-cores will keep wakeup status::
-
- testpmd>set fwd txonly
- testpmd>start
-
-4. Stop and restart testpmd again, check vhost-user cores will sleep and wakeup again.
\ No newline at end of file
--
2.25.1
reply other threads:[~2022-05-19 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220519081353.2816053-1-weix.ling@intel.com \
--to=weix.ling@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).