From: "zhao,meijuan" <meijuanx.zhao@intel.com>
To: dts@dpdk.org
Cc: "zhao,meijuan" <meijuanx.zhao@intel.com>
Subject: [dts] [PATCH V2 2/2] test_plan/vf packet rxtx: add dpdk pf + dpdk vf test scenario
Date: Wed, 6 Jun 2018 10:54:02 +0800 [thread overview]
Message-ID: <1528253642-46578-2-git-send-email-meijuanx.zhao@intel.com> (raw)
In-Reply-To: <1528253642-46578-1-git-send-email-meijuanx.zhao@intel.com>
add dpdk pf + dpdk vf test scenario
Signed-off-by: zhao,meijuan <meijuanx.zhao@intel.com>
---
test_plans/vf_packet_rxtx_test_plan.rst | 232 +++++++++++++++++++++++++++++++-
1 file changed, 227 insertions(+), 5 deletions(-)
diff --git a/test_plans/vf_packet_rxtx_test_plan.rst b/test_plans/vf_packet_rxtx_test_plan.rst
index 0df9984..e455288 100644
--- a/test_plans/vf_packet_rxtx_test_plan.rst
+++ b/test_plans/vf_packet_rxtx_test_plan.rst
@@ -41,7 +41,7 @@ Test Case 1: VF_packet_IO_kernel_PF_dpdk_VF
1. Got the pci device id of DUT, for example::
- ./dpdk_nic_bind.py --st
+ ./usertools/dpdk-devbind.py -s
0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=i40e unused=
0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=i40e unused=
@@ -50,7 +50,7 @@ Test Case 1: VF_packet_IO_kernel_PF_dpdk_VF
echo 1 > /sys/bus/pci/devices/0000\:81\:00.0/sriov_numvfs
echo 1 > /sys/bus/pci/devices/0000\:81\:00.1/sriov_numvfs
- ./dpdk_nic_bind.py --st
+ ./usertools/dpdk-devbind.py -s
0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=i40e unused=
0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=i40e unused=
@@ -76,7 +76,7 @@ Test Case 1: VF_packet_IO_kernel_PF_dpdk_VF
virsh nodedev-detach pci_0000_81_02_0;
virsh nodedev-detach pci_0000_81_0a_0;
- ./dpdk_nic_bind.py --st
+ ./usertools/dpdk-devbind.py -s
0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=i40e unused=
0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=i40e unused=
@@ -95,12 +95,234 @@ Test Case 1: VF_packet_IO_kernel_PF_dpdk_VF
5. Login vm0, got VFs pci device id in vm0, assume they are 00:06.0 & 00:07.0, bind them to igb_uio driver,
and then start testpmd, set it in mac forward mode::
- ./tools/dpdk_nic_bind.py --bind=igb_uio 00:06.0 00:07.0
+ ./usertools/dpdk-devbind.py --bind=igb_uio 00:06.0 00:07.0
./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 -w 00:06.0 -w 00:07.0 \
- -- -i --portmask=0x3 --tx-offloads=0x8fff
+ -- -i
testpmd> set fwd mac
testpmd> start
6. Get mac address of one VF and use it as dest mac, using scapy to send 2000 random packets from tester,
verify the packets can be received by one VF and can be forward to another VF correctly.
+
+
+Test Case 2: VF_packet_IO_dpdk_PF_dpdk_VF
+===========================================
+
+1. Got the pci device id of DUT, for example::
+
+ ./usertools/dpdk-devbind.py -s
+
+ 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=i40e unused=
+ 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=i40e unused=
+
+2. bind pf to igb_uio and Create 2 VFs from 2 PFs::
+
+ ./usertools/dpdk-devbind.py --bind=igb_uio 0000:81:00.0 0000:81:00.1
+ echo 1 > /sys/bus/pci/devices/0000\:81\:00.0/max_vfs
+ echo 1 > /sys/bus/pci/devices/0000\:81\:00.1/max_vfs
+
+3. Detach VFs from the host, bind them to pci-stub driver::
+
+ /sbin/modprobe pci-stub
+
+ using `lspci -nn|grep -i ethernet` got VF device id, for example "8086 154c",
+
+ echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo 0000:81:02.0 > /sys/bus/pci/devices/0000:08:02.0/driver/unbind
+ echo 0000:81:02.0 > /sys/bus/pci/drivers/pci-stub/bind
+
+ echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo 0000:81:0a.0 > /sys/bus/pci/devices/0000:08:0a.0/driver/unbind
+ echo 0000:81:0a.0 > /sys/bus/pci/drivers/pci-stub/bind
+
+ or using the following more easy way::
+
+ virsh nodedev-detach pci_0000_81_02_0;
+ virsh nodedev-detach pci_0000_81_0a_0;
+
+ ./usertools/dpdk-devbind.py -s
+
+ 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=i40e unused=
+ 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=i40e unused=
+ 0000:81:02.0 'XL710/X710 Virtual Function' if= drv=pci-stub unused=
+ 0000:81:0a.0 'XL710/X710 Virtual Function' if= drv=pci-stub unused=
+
+ it can be seen that VFs 81:02.0 & 81:0a.0 's drv is pci-stub.
+4. Start testpmd on host::
+
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x3e -n 4 -b 0000:81:02.0 -b 0000:81:0a.0 -- -i
+
+5. Passthrough VFs 81:02.0 & 81:0a.0 to vm0, and start vm0::
+
+ /usr/bin/qemu-system-x86_64 -name vm0 -enable-kvm \
+ -cpu host -smp 4 -m 2048 -drive file=/home/image/sriov-fc20-1.img -vnc :1 \
+ -device pci-assign,host=81:02.0,id=pt_0 \
+ -device pci-assign,host=81:0a.0,id=pt_1
+
+6. Login vm0, got VFs pci device id in vm0, assume they are 00:06.0 & 00:07.0, bind them to igb_uio driver,
+ and then start testpmd, set it in mac forward mode::
+
+ ./usertools/dpdk-devbind.py --bind=igb_uio 00:06.0 00:07.0
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x0f -n 4 -w 00:06.0 -w 00:07.0 \
+ -- -i
+
+ testpmd> set fwd mac
+ testpmd> start
+
+7. Get mac address of one VF and use it as dest mac, using scapy to send 2000 random packets from tester,
+ verify the packets can be received by one VF and can be forward to another VF correctly.
+
+Test Case 3: pf dpdk vf reset
+===========================================
+this case pf in dpdk
+===========================================
+
+1. Got the pci device id of DUT, for example::
+
+ ./usertools/dpdk-devbind.py -s
+
+ 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=i40e unused=
+ 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=i40e unused=
+
+2. bind pf to igb_uio and Create 3 VFs from pf0::
+
+ ./usertools/dpdk-devbind.py --bind=igb_uio 0000:81:00.0
+ echo 3 > /sys/bus/pci/devices/0000\:81\:00.0/max_vfs
+
+
+3. Detach VFs from the host, bind them to pci-stub driver::
+
+ /sbin/modprobe pci-stub
+
+ using `lspci -nn|grep -i ethernet` got VF device id, for example "8086 154c",
+
+ echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo 0000:81:02.0 > /sys/bus/pci/devices/0000:08:02.0/driver/unbind
+ echo 0000:81:02.0 > /sys/bus/pci/drivers/pci-stub/bind
+
+ echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo 0000:81:02.1 > /sys/bus/pci/devices/0000:08:02.1/driver/unbind
+ echo 0000:81:02.1 > /sys/bus/pci/drivers/pci-stub/bind
+
+ echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo 0000:81:02.2 > /sys/bus/pci/devices/0000:08:02.2/driver/unbind
+ echo 0000:81:02.2 > /sys/bus/pci/drivers/pci-stub/bind
+
+
+ it can be seen that VFs 81:02.0 & 81:02.1 & 81:02.2 's drv is pci-stub.
+4. Start testpmd on host::
+
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x600000000006 -n 4 -b 0000:81:02.0 -b 0000:81:02.1 -b 0000:81:02.2 -- -i
+
+5. Passthrough VFs 81:02.0 & 81:02.1 to vm0, and start vm0::
+
+ /usr/bin/qemu-system-x86_64 -name vm0 -enable-kvm \
+ -cpu host -smp 4 -m 2048 -drive file=/home/image/sriov-fc20-1.img -vnc :1 \
+ -device pci-assign,host=81:02.0,id=pt_0 \
+ -device pci-assign,host=81:02.1,id=pt_1
+6. Passthrough VFs 81:02.2 to vm1, and start vm1::
+
+ /usr/bin/qemu-system-x86_64 -name vm0 -enable-kvm \
+ -cpu host -smp 4 -m 2048 -drive file=/home/image/sriov-fc20-2.img -vnc :2 \
+ -device pci-assign,host=81:02.2,id=pt_0
+
+7. Login vm0 and vm1, got VFs pci device id in vm0 and vm1, assume they are 00:04.0 & 00:05.0 on vm0,00:04.0 on vm1, bind them to igb_uio driver,for vm0::
+
+ ./usertools/dpdk-devbind.py --bind=igb_uio 00:04.0 00:05.0
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 1 -- -i
+ testpmd> set fwd mac
+ testpmd> start
+8. On vm 1::
+
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 1 -- -i
+
+9. On vm0::
+
+ testpmd>clear port stats all
+
+10. Tester loop send packet to vf0 on vm0
+
+11. On vm1 loop start stop port 1000 times::
+
+ testpmd>port stop all
+ testpmd>port start all
+
+12. Tester stop send packet
+
+13. On vm0,check port stats,verify vf0 vf1 can receive packet ,no error
+
+
+Test Case 4: pf kernel vf reset
+===========================================
+this case pf in kernel
+===========================================
+
+1. Got the pci device id of DUT, for example::
+
+ ./usertools/dpdk-devbind.py -s
+
+ 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=i40e unused=
+ 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=i40e unused=
+
+2. bind pf to igb_uio and Create 3 VFs from pf0::
+
+ echo 3 > /sys/bus/pci/devices/0000\:81\:00.0/sriov_nums
+
+
+3. Detach VFs from the host, bind them to pci-stub driver::
+
+ /sbin/modprobe pci-stub
+
+ using `lspci -nn|grep -i ethernet` got VF device id, for example "8086 154c",
+
+ echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo 0000:81:02.0 > /sys/bus/pci/devices/0000:08:02.0/driver/unbind
+ echo 0000:81:02.0 > /sys/bus/pci/drivers/pci-stub/bind
+
+ echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo 0000:81:02.1 > /sys/bus/pci/devices/0000:08:02.1/driver/unbind
+ echo 0000:81:02.1 > /sys/bus/pci/drivers/pci-stub/bind
+
+ echo "8086 154c" > /sys/bus/pci/drivers/pci-stub/new_id
+ echo 0000:81:02.2 > /sys/bus/pci/devices/0000:08:02.2/driver/unbind
+ echo 0000:81:02.2 > /sys/bus/pci/drivers/pci-stub/bind
+
+
+ it can be seen that VFs 81:02.0 & 81:02.1 & 81:02.2 's drv is pci-stub.
+
+4. Passthrough VFs 81:02.0 & 81:02.1 to vm0, and start vm0::
+
+ /usr/bin/qemu-system-x86_64 -name vm0 -enable-kvm \
+ -cpu host -smp 4 -m 2048 -drive file=/home/image/sriov-fc20-1.img -vnc :1 \
+ -device pci-assign,host=81:02.0,id=pt_0 \
+ -device pci-assign,host=81:02.1,id=pt_1
+5. Passthrough VFs 81:02.2 to vm1, and start vm1::
+
+ /usr/bin/qemu-system-x86_64 -name vm0 -enable-kvm \
+ -cpu host -smp 4 -m 2048 -drive file=/home/image/sriov-fc20-2.img -vnc :2 \
+ -device pci-assign,host=81:02.2,id=pt_0
+
+6. Login vm0 and vm1, got VFs pci device id in vm0 and vm1, assume they are 00:04.0 & 00:05.0 on vm0,00:04.0 on vm1, bind them to igb_uio driver,for vm0::
+
+ ./usertools/dpdk-devbind.py --bind=igb_uio 00:04.0 00:05.0
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 1 -- -i
+ testpmd> set fwd mac
+ testpmd> start
+7. On vm 1::
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 1 -- -i
+
+8. On vm0::
+
+ testpmd>clear port stats all
+
+9. Tester loop send packet to vf0 on vm0
+
+10. On vm1 loop start stop port 1000 times::
+
+ testpmd>port stop all
+ testpmd>port start all
+
+11. Tester stop send packet
+
+12. On vm0,check port stats,verify vf0 vf1 can receive packet ,no error
--
1.9.3
next prev parent reply other threads:[~2018-06-06 2:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 2:54 [dts] [PATCH V2 1/2] tests/vf packet rxtx : " zhao,meijuan
2018-06-06 2:54 ` zhao,meijuan [this message]
2018-06-11 13:50 ` [dts] [PATCH V2 2/2] test_plan/vf packet rxtx: " Liu, Yong
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=1528253642-46578-2-git-send-email-meijuanx.zhao@intel.com \
--to=meijuanx.zhao@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).