test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Zhang, Yuwei1" <yuwei1.zhang@intel.com>
To: "Zhu, WenhuiX" <wenhuix.zhu@intel.com>,
	"Zhang, YanX A" <yanx.a.zhang@intel.com>,
	"dts@dpdk.org" <dts@dpdk.org>
Cc: "Zhang, YanX A" <yanx.a.zhang@intel.com>
Subject: Re: [dts] [PATCH V1] test_plans/vf_interrupt_pmd_test_plan:Modify test	plan
Date: Tue, 6 Aug 2019 01:58:21 +0000	[thread overview]
Message-ID: <EC241D52C34C9A4BA57BFACAB76C70A43CD9E363@SHSMSX105.ccr.corp.intel.com> (raw)
In-Reply-To: <E08767FB2CE10642B6780736EAC070F6049A9529@shsmsx102.ccr.corp.intel.com>

Acked-by: Zhang, Yuwei

-----Original Message-----
From: Zhu, WenhuiX 
Sent: Monday, August 5, 2019 4:46 PM
To: Zhang, YanX A <yanx.a.zhang@intel.com>; dts@dpdk.org
Cc: Zhang, Yuwei1 <yuwei1.zhang@intel.com>; Zhang, YanX A <yanx.a.zhang@intel.com>
Subject: RE: [dts] [PATCH V1] test_plans/vf_interrupt_pmd_test_plan:Modify test plan


Tested-by: Zhu, WenhuiX <wenhuix.zhu@intel.com>

-----Original Message-----
From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of zhang,yan
Sent: Monday, August 5, 2019 4:34 PM
To: dts@dpdk.org
Cc: Zhang, Yuwei1 <yuwei1.zhang@intel.com>; Zhang, YanX A <yanx.a.zhang@intel.com>
Subject: [dts] [PATCH V1] test_plans/vf_interrupt_pmd_test_plan:Modify test plan

Modify test_plan.

Signed-off-by: zhang,yan <yanx.a.zhang@intel.com>
---
 test_plans/vf_interrupt_pmd_test_plan.rst | 131 +++++++++-------------
 1 file changed, 51 insertions(+), 80 deletions(-)

diff --git a/test_plans/vf_interrupt_pmd_test_plan.rst b/test_plans/vf_interrupt_pmd_test_plan.rst
index 1c4bb7d..6464ebc 100644
--- a/test_plans/vf_interrupt_pmd_test_plan.rst
+++ b/test_plans/vf_interrupt_pmd_test_plan.rst
@@ -1,4 +1,4 @@
-.. Copyright (c) <2017>, Intel Corporation
+.. Copyright (c) <2017-2019>, Intel Corporation
    All rights reserved.
 
    Redistribution and use in source and binary forms, with or without @@ -49,123 +49,94 @@ Prerequisites  Each of the 10Gb Ethernet* ports of the DUT is directly connected in  full-duplex to a different port of the peer traffic generator.
 
-Assume PF port PCI addresses are 0000:04:00.0 and 0000:04:00.1, their -Interfaces name are p786p1 and p786p2. Assume generated VF PCI address will -be 0000:04:10.0, 0000:04:10.1.
+Assume PF port PCI addresses is 0000:04:00.0, their Interfaces name is 
+p786p0. Assume generated VF PCI address will be 0000:04:10.0.
 
 Iommu pass through feature has been enabled in kernel::
 
-   intel_iommu=on iommu=pt
+    intel_iommu=on iommu=pt
 
-Support igb_uio and vfio driver, if used vfio, kernel need 3.6+ and enable vt-d -in bios. When used vfio, requested to insmod two drivers vfio and vfio-pci.
-
-Test Case1: VF interrupt pmd in VM with uio -===========================================
-
-Create one VF per Port in host and add these two VFs into VM::
-
-
-   usertools/dpdk-devbind.py --force --bind=vfio-pci 0000:04:00.0 0000:04:00.1
-        echo 1 >/sys/bus/pci/devices/0000\:04\:00.0/max_vfs
-        echo 1 >/sys/bus/pci/devices/0000\:04\:00.1/max_vfs
-        usertools/dpdk-devbind.py --force --bind=pci-stub 0000:04:10.0 0000:04:10.1
-
-Start VM and start l3fwd-power with one queue per port in VM::
+Modify the DPDK-l3fwd-power source code and recompile the l3fwd-power::
 
+    sed -i -e '/DEV_RX_OFFLOAD_CHECKSUM,/d' 
+ ./examples/l3fwd-power/main.c
 
-   l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
+    export RTE_TARGET=x86_64-native-linuxapp-gcc
+    export RTE_SDK=`/root/DPDK`
+    make -C examples/l3fwd-power
 
-Send one packet to VF0 and VF1, check that thread on core1 and core2 waked up::
-
-
-   L3FWD_POWER: lcore 1 is waked up from rx interrupt on port1,rxq0
-   L3FWD_POWER: lcore 2 is waked up from rx interrupt on port1,rxq0
-
-Check the packet has been normally forwarded.
-
-After the packet forwarded, thread on core1 and core 2 will return to sleep::
-
-   L3FWD_POWER: lcore 1 sleeps until interrupt on port0,rxq0 triggers
-   L3FWD_POWER: lcore 2 sleeps until interrupt on port0,rxq0 triggers
+Support igb_uio and vfio driver, if used vfio, kernel need 3.6+ and 
+enable vt-d in bios. When used vfio, requested to insmod two drivers vfio and vfio-pci.
 
-Send packet flows to VF0 and VF1, check that thread on core1 and core2 will -keep up awake.
+Test Case1: Check Interrupt for PF with vfio driver on ixgbe and i40e 
+=====================================================================
 
-Test Case2: VF interrupt pmd in Host with uio -=============================================
+1. Bind NIC PF to igb_uio drvier::
 
-Create one VF per Port in host and make sure PF interface up -uses kernel driver to create vf::
+    modprobe vfio-pci;
 
+    usertools/dpdk-devbind.py --bind=igb-uio 0000:04:00.0
 
-        echo 1 >/sys/bus/pci/devices/0000\:04\:00.1/sriov_numvf
-        echo 1 >/sys/bus/pci/devices/0000\:04\:00.1/sriov_numvf
+2. start l3fwd-power with PF::
 
-Bind VF device to igb_uio::
+    examples/l3fwd-power/build/l3fwd-power -l 1-3 -n 4 -- -P -p 0x01  --config '(0,0,2)'
 
+3. Send packet with packet generator to the pf NIC, check that thread core2 waked up::
 
-   ./usertools/dpdk-devbind.py --bind=igb_uio 0000:04:10.0 0000:04:10.1
+    
+ sendp([Ether(dst='pf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')],
+ iface="tester_intf")
 
-Start host and start l3fwd-power with one queue per port in host::
+    L3FWD_POWER: lcore 2 is waked up from rx interrupt on port 0 queue
+ 0
 
+4. Check if threads on core 2 have returned to sleep mode::
 
-   l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
+    L3FWD_POWER: lcore 2 sleeps until interrupt triggers
 
-Send one packet to VF0 and VF1, check that thread on core1 and core2 waked up::
+Test Case2: Check Interrupt for PF with igb_uio driver on ixgbe and 
+i40e 
+=======================================================================
+=
 
+1. Bind NIC PF to igb_uio drvier::
 
-   L3FWD_POWER: lcore 1 is waked up from rx interrupt on port1,rxq0
-   L3FWD_POWER: lcore 2 is waked up from rx interrupt on port1,rxq0
+    modprobe uio;
+    insmod x86_64-native-linuxapp-gcc/kmod/igb_uio.ko;
 
-Check the packet has been normally forwarded.
+    usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:00.0
 
-After the packet forwarded, thread on core1 and core 2 will return to sleep::
+2. start l3fwd-power with PF::
 
-   L3FWD_POWER: lcore 1 sleeps until interrupt on port0,rxq0 triggers
-   L3FWD_POWER: lcore 2 sleeps until interrupt on port0,rxq0 triggers
+    examples/l3fwd-power/build/l3fwd-power -l 1-3 -n 4 -- -P -p 0x01  --config '(0,0,2)'
 
-Send packet flows to VF0 and VF1, check that thread on core1 and core2 will -keep up awake.
+3. Send packet with packet generator to the pf NIC, check that thread core2 waked up::
 
-Test Case3: VF interrupt pmd in Host with vfio -==============================================
+    
+ sendp([Ether(dst='pf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')],
+ iface="tester_intf")
 
-Create one VF per Port in host and make sure PF interface up -uses kernel driver to create vf::
+    L3FWD_POWER: lcore 2 is waked up from rx interrupt on port 0 queue
+ 0
 
+4. Check if threads on core 2 have returned to sleep mode::
 
-        echo 1 >/sys/bus/pci/devices/0000\:04\:00.1/sriov_numvf
-        echo 1 >/sys/bus/pci/devices/0000\:04\:00.1/sriov_numvf
+    L3FWD_POWER: lcore 2 sleeps until interrupt triggers
 
-Bind VF device to host igb_uio::
+Test Case3: Check Interrupt for VF with vfio driver on ixgbe and i40e 
+=====================================================================
 
+1. Generate NIC VF, then bind it to vfio drvier::
 
-   ./usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:10.0 0000:04:10.1
+    echo 1 > /sys/bus/pci/devices/0000\:04\:00.0/sriov_numvfs
 
-Start VM and start l3fwd-power with two queues per port in VM::
+    modprobe vfio-pci
+    usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:10.0(vf_pci)
 
+  Notice:  If your PF is kernel driver, make sure PF link is up when your start testpmd on VF.
 
-   l3fwd-power -c 1f -n 4 -- -p 0x3 -P \
-      --config="(0,0,1),(0,1,2)(1,0,3),(1,1,4)"
+2. Start l3fwd-power with VF::
 
-Send packets with increased dest IP to Port0 and Port1, check that thread on
-core1,core2,core3,core4 waked up::
+    examples/l3fwd-power/build/l3fwd-power -l 1-3 -n 4 -- -P -p 0x01  --config '(0,0,2)'
 
-   L3FWD_POWER: lcore 1 is waked up from rx interrupt on port1,rxq0
-   L3FWD_POWER: lcore 2 is waked up from rx interrupt on port1,rxq1
-   L3FWD_POWER: lcore 3 is waked up from rx interrupt on port1,rxq0
-   L3FWD_POWER: lcore 4 is waked up from rx interrupt on port1,rxq1
+3. Send packet with packet generator to the pf NIC, check that thread core2 waked up::
 
-Check the packet has been normally forwarded.
+    
+ sendp([Ether(dst='vf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')],
+ iface="tester_intf")
 
-After the packet forwarded, thread on core1,core2,core3,core4 will return to
-sleep::
+    L3FWD_POWER: lcore 2 is waked up from rx interrupt on port 0 queue
+ 0
 
-   L3FWD_POWER: lcore 1 sleeps until interrupt on port0,rxq0 triggers
-   L3FWD_POWER: lcore 2 sleeps until interrupt on port0,rxq1 triggers
-   L3FWD_POWER: lcore 3 sleeps until interrupt on port1,rxq0 triggers
-   L3FWD_POWER: lcore 4 sleeps until interrupt on port1,rxq1 triggers
+4. Check if threads on core 2 have returned to sleep mode::
 
-Send packet flows to Port0 and Port1, check that thread on core1,core2,core3,
-core4 will keep up awake.
+    L3FWD_POWER: lcore 2 sleeps until interrupt triggers
--
2.17.2


      reply	other threads:[~2019-08-06  1:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-05  8:34 zhang,yan
2019-08-05  8:45 ` Zhu, WenhuiX
2019-08-06  1:58   ` Zhang, Yuwei1 [this message]

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=EC241D52C34C9A4BA57BFACAB76C70A43CD9E363@SHSMSX105.ccr.corp.intel.com \
    --to=yuwei1.zhang@intel.com \
    --cc=dts@dpdk.org \
    --cc=wenhuix.zhu@intel.com \
    --cc=yanx.a.zhang@intel.com \
    /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).