From: "zhao,meijuan" <meijuanx.zhao@intel.com>
To: dts@dpdk.org
Cc: "zhao,meijuan" <meijuanx.zhao@intel.com>
Subject: [dts] [PATCH V1] test_plan/vf macfilter : add dpdk pf + dpdk vf scenario
Date: Wed, 4 Apr 2018 14:21:10 +0800 [thread overview]
Message-ID: <1522822870-110299-1-git-send-email-meijuanx.zhao@intel.com> (raw)
add dpdk pf + dpdk vf scenario
Signed-off-by: zhao,meijuan <meijuanx.zhao@intel.com>
---
test_plans/vf_macfilter_test_plan.rst | 173 ++++++++++++++++++++++++++++++++++
1 file changed, 173 insertions(+)
diff --git a/test_plans/vf_macfilter_test_plan.rst b/test_plans/vf_macfilter_test_plan.rst
index 221c05e..bf7bd4e 100644
--- a/test_plans/vf_macfilter_test_plan.rst
+++ b/test_plans/vf_macfilter_test_plan.rst
@@ -199,3 +199,176 @@ Test Case 2: test_kernel_2pf_2vf_1vm_mac_add_filter
8. Use scapy to send 100 random packets with a wrong MAC to VF0, verify the
packets can't be received by one VF and can be forward to another VF
correctly.
+
+
+Test Case 3: test_dpdk_2pf_2vf_1vm_iplink_macfilter
+=====================================================
+
+1. Get the pci device id of DUT, for example::
+
+ ./dpdk_nic_bind.py --st
+
+ 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=
+
+ usertools/dpdk-devbind.py --force --bind=igb_uio 0000:81:00.0 0000:81:00.0
+
+2. Create 2 VFs from 2 PFs, and set the VF MAC address at PF0::
+
+ echo 1 > /sys/bus/pci/devices/0000\:81\:00.0/max_vfs
+ echo 1 > /sys/bus/pci/devices/0000\:81\:00.1/max_vfs
+
+ ./dpdk_nic_bind.py --st
+ 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=igb_uio unused=
+ 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=igb_uio unused=
+ 0000:81:02.0 'XL710/X710 Virtual Function' unused=
+ 0000:81:0a.0 'XL710/X710 Virtual Function' unused=
+
+
+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;
+
+ ./dpdk_nic_bind.py --st
+
+ 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=igb_uio unused=
+ 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=igb_uio 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 driver is pci-stub.
+4. on host start testpmd
+
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x6000000006 -n 4 -b 0000:81:02.0 -b 0000:81:0a.0 -- -i
+ testpmd > set vf mac addr 0 0 00:12:34:56:78:01
+
+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, enable CRC strip,
+ disable promisc mode,set it in mac forward mode::
+
+ ./tools/dpdk_nic_bind.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
+ testpmd> set promisc all off
+ testpmd> set fwd mac
+ testpmd> start
+
+7. Use scapy to send 100 random packets with ip link set MAC to VF, verify the
+ packets can be received by one VF and can be forward to another VF
+ correctly.
+
+8. Also use scapy to send 100 random packets with a wrong MAC to VF, verify
+ the packets can't be received by one VF and can be forward to another VF
+ correctly.
+
+Test Case 4: test_dpdk_2pf_2vf_1vm_mac_add_filter
+===================================================
+
+1. Get the pci device id of DUT, for example::
+
+ ./dpdk_nic_bind.py --st
+
+ 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=
+
+ usertools/dpdk-devbind.py --force --bind=igb_uio 0000:81:00.0 0000:81:00.0
+
+2. Create 2 VFs from 2 PFs, and don't set the VF MAC address at PF0::
+
+
+ echo 1 > /sys/bus/pci/devices/0000\:81\:00.0/max_vfs
+ echo 1 > /sys/bus/pci/devices/0000\:81\:00.1/max_vfs
+
+ ./dpdk_nic_bind.py --st
+ 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=igb_uio unused=
+ 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=igb_uio unused=
+ 0000:81:02.0 'XL710/X710 Virtual Function' unused=
+ 0000:81:0a.0 'XL710/X710 Virtual Function' unused=
+
+3. Detach VFs from the host, bind them to pci-stub driver::
+
+ /sbin/modprobe pci-stub
+
+ using `lspci -nn|grep -i ethernet` to get 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;
+
+ ./dpdk_nic_bind.py --st
+
+ 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f0 drv=igb_uio unused=
+ 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+' if=ens259f1 drv=igb_uio 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 driver is pci-stub.
+
+4. On host start testpmd
+
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0x6000000006 -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, enable CRC strip on
+ VF, disable promisc mode, add a new MAC to VF0 and then start::
+
+ ./tools/dpdk_nic_bind.py --bind=igb_uio 00:06.0 00:07.0
+ ./x86_64-native-linuxapp-gcc/app/testpmd -c 0xf -n 1 -- -i
+ testpmd> set promisc all off
+ testpmd> mac_addr add 0 00:11:22:33:44:55
+ testpmd> set fwd mac
+ testpmd> start
+
+ Note: In Jan, 2016, i40e doesn't support mac_addr add operation, so the
+ case will be failed for FVL/Fort park NICs.
+
+7. Use scapy to send 100 random packets with current VF0's MAC, verify the
+ packets can be received by one VF and can be forward to another VF
+ correctly.
+
+8. Use scapy to send 100 random packets with new added VF0's MAC, verify the
+ packets can be received by one VF and can be forward to another VF
+ correctly.
+
+9. Use scapy to send 100 random packets with a wrong MAC to VF0, verify the
+ packets can't be received by one VF and can be forward to another VF
+ correctly.
+
+
--
1.9.3
next reply other threads:[~2018-04-04 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 6:21 zhao,meijuan [this message]
2018-04-20 1:14 ` Liu, Yong
2018-04-20 3:28 [dts] [PATCH V1] test_plan/vf macfilter " zhao,meijuan
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=1522822870-110299-1-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).