From: Yinan Wang <yinan.wang@intel.com>
To: dts@dpdk.org
Cc: Yinan Wang <yinan.wang@intel.com>
Subject: [dts] [PATCH v1] test_plans/virtio_event_idx_interrupt_test_plan.rst
Date: Fri, 21 Aug 2020 06:31:43 -0400 [thread overview]
Message-ID: <20200821103143.47710-1-yinan.wang@intel.com> (raw)
Add cbdma enabled interrupt cases
Signed-off-by: Yinan Wang <yinan.wang@intel.com>
---
.../virtio_event_idx_interrupt_test_plan.rst | 99 ++++++++++++++++++-
1 file changed, 98 insertions(+), 1 deletion(-)
diff --git a/test_plans/virtio_event_idx_interrupt_test_plan.rst b/test_plans/virtio_event_idx_interrupt_test_plan.rst
index 8293032..1fbadee 100644
--- a/test_plans/virtio_event_idx_interrupt_test_plan.rst
+++ b/test_plans/virtio_event_idx_interrupt_test_plan.rst
@@ -256,4 +256,101 @@ Test Case 6: Wake up packed ring virtio-net cores with event idx interrupt mode
testpmd>stop
testpmd>start
- testpmd>stop
\ No newline at end of file
+ testpmd>stop
+
+Test Case 7: wake up vhost-user core with event idx interrupt mode and cbdma enabled
+====================================================================================
+
+1. Launch l3fwd-power example app with client mode::
+
+ ./examples/l3fwd-power/build/l3fwd-power -l 1 -w 80:04.0 \
+ -n 4 \
+ --log-level=9 \
+ --vdev 'eth_vhost0,iface=/vhost-net0,queues=1,client=1,dmas=[txq0@80:04.0],dmathr=1024' \
+ -- -p 0x1 \
+ --parse-ptype 1 \
+ --config "(0,0,1)"
+
+2. Launch VM1 with server mode::
+
+ taskset -c 33 \
+ /home/qemu-install/qemu-3.0/bin/qemu-system-x86_64 -name us-vhost-vm1 \
+ -cpu host -enable-kvm -smp cores=1,sockets=1 -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem -mem-prealloc -drive file=/home/osimg/ubuntu1910.img -netdev user,id=yinan,hostfwd=tcp:127.0.0.1:6006-:22 -device e1000,netdev=yinan \
+ -chardev socket,server,id=char0,path=/vhost-net0 \
+ -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
+ -device virtio-net-pci,mac=52:54:00:00:00:01,netdev=mynet1,csum=on -vnc :10 -daemonize
+
+3. Relauch l3fwd-power sample for port up::
+
+ ./examples/l3fwd-power/build/l3fwd-power -l 1 -w 80:04.0 \
+ -n 4 \
+ --log-level=9 \
+ --vdev 'eth_vhost0,iface=/vhost-net0,queues=1,client=1,dmas=[txq0@80:04.0],dmathr=1024' \
+ -- -p 0x1 \
+ --parse-ptype 1 \
+ --config "(0,0,1)"
+
+3. On VM, set ip for virtio device and send packets to vhost::
+
+ ifconfig [ens3] 1.1.1.2 # [ens3] is the name of virtio-net
+ ping 1.1.1.3
+
+4. Check vhost related core is waked up by reading l3fwd-power log.
+
+Test Case 8: wake up vhost-user cores with event idx interrupt mode and cbdma enabled 16 queues test
+====================================================================================================
+
+1. Launch l3fwd-power example app with client mode::
+
+ ./examples/l3fwd-power/build/l3fwd-power -l 1-16 \
+ -n 4 --socket-mem 1024,1024 --legacy-mem \
+ --log-level=9 \
+ --vdev 'eth_vhost0,iface=/vhost-net0,queues=16,client=1,dmas=[txq0@80:04.0;txq1@80:04.1;txq2@80:04.2;txq3@80:04.3;txq4@80:04.4;txq5@80:04.5;txq6@80:04.6;txq7@80:04.7;txq8@00:04.0;txq9@00:04.1;txq10@00:04.2;txq11@00:04.3;txq12@00:04.4;txq13@00:04.5;txq14@00:04.6;txq15@00:04.7],dmathr=1024' \
+ -- -p 0x1 \
+ --parse-ptype 1 \
+ --config "(0,0,1),(0,1,2),(0,2,3),(0,3,4),(0,4,5),(0,5,6),(0,6,7),(0,7,8),(0,8,9),(0,9,10),(0,10,11),(0,11,12),(0,12,13),(0,13,14),(0,14,15),(0,15,16)"
+
+2. Launch VM1 with server mode::
+
+ taskset -c 17-18 /home/qemu-install/qemu-3.0/bin/qemu-system-x86_64 -name us-vhost-vm1 -cpu host -enable-kvm -m 2048 -object memory-backend-file,id=mem,size=2048M,mem-path=/mnt/huge,share=on -numa node,memdev=mem -mem-prealloc -netdev user,id=yinan,hostfwd=tcp:127.0.0.1:6001-:22 -device e1000,netdev=yinan -smp cores=16,sockets=1 -drive file=/home/osimg/ubuntu1910.img -chardev socket,server,id=char0,path=/vhost-net0 -netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce,queues=16 -device virtio-net-pci,mac=52:54:00:00:00:01,netdev=mynet1,csum=on,mq=on,vectors=40 -vnc :10 -daemonize
+
+3. Relauch l3fwd-power sample for port up::
+
+ ./examples/l3fwd-power/build/l3fwd-power -l 1-16 \
+ -n 4 --socket-mem 1024,1024 --legacy-mem \
+ --log-level=9 \
+ --vdev 'eth_vhost0,iface=/vhost-net0,queues=16,client=1,dmas=[txq0@80:04.0;txq1@80:04.1;txq2@80:04.2;txq3@80:04.3;txq4@80:04.4;txq5@80:04.5;txq6@80:04.6;txq7@80:04.7;txq8@00:04.0;txq9@00:04.1;txq10@00:04.2;txq11@00:04.3;txq12@00:04.4;txq13@00:04.5;txq14@00:04.6;txq15@00:04.7],dmathr=1024' \
+ -- -p 0x1 \
+ --parse-ptype 1 --interrupt-only \
+ --config "(0,0,1),(0,1,2),(0,2,3),(0,3,4),(0,4,5),(0,5,6),(0,6,7),(0,7,8),(0,8,9),(0,9,10),(0,10,11),(0,11,12),(0,12,13),(0,13,14),(0,14,15),(0,15,16)"
+
+3. Set vitio-net with 16 quques and give vitio-net ip address::
+
+ ethtool -L ens4 combined 16 # [ens3] is the name of virtio-net
+ ifconfig ens4 1.1.1.1
+
+4. Send packets with different IPs from virtio-net, notice to bind each vcpu to different send packets process::
+
+ taskset -c 0 ping 1.1.1.2
+ taskset -c 1 ping 1.1.1.3
+ taskset -c 2 ping 1.1.1.4
+ taskset -c 3 ping 1.1.1.5
+ taskset -c 4 ping 1.1.1.6
+ taskset -c 5 ping 1.1.1.7
+ taskset -c 6 ping 1.1.1.8
+ taskset -c 7 ping 1.1.1.9
+ taskset -c 8 ping 1.1.1.2
+ taskset -c 9 ping 1.1.1.2
+ taskset -c 10 ping 1.1.1.2
+ taskset -c 11 ping 1.1.1.2
+ taskset -c 12 ping 1.1.1.2
+ taskset -c 13 ping 1.1.1.2
+ taskset -c 14 ping 1.1.1.2
+ taskset -c 15 ping 1.1.1.2
+
+5. Check vhost related cores are waked up with l3fwd-power log, such as following::
+
+ L3FWD_POWER: lcore 0 is waked up from rx interrupt on port 0 queue 0
+ .....
+ .....
+ L3FWD_POWER: lcore 15 is waked up from rx interrupt on port 0 queue 15
--
2.17.1
next reply other threads:[~2020-08-21 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 10:31 Yinan Wang [this message]
2020-08-27 2:02 ` Tu, Lijuan
2020-09-22 16:27 Yinan Wang
2020-10-12 7:45 ` Tu, Lijuan
2020-09-23 16:48 Yinan Wang
2020-10-12 7:42 ` Tu, Lijuan
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=20200821103143.47710-1-yinan.wang@intel.com \
--to=yinan.wang@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).