From: "xu,gang" <gangx.xu@intel.com>
To: dts@dpdk.org
Cc: "xu,gang" <gangx.xu@intel.com>
Subject: [dts] [PATCH V1] modify the interrupt pmd test plan
Date: Fri, 9 Jun 2017 14:08:14 +0800 [thread overview]
Message-ID: <1496988494-73053-1-git-send-email-gangx.xu@intel.com> (raw)
merge PF interrupt pmd test with uio vfio mode and check state with different queue in it
remove VF interrupt pmd test case to VF interrupt pmd test suite
Signed-off-by: xu,gang <gangx.xu@intel.com>
---
test_plans/interrupt_pmd_test_plan.rst | 170 ++++-----------------------------
1 file changed, 19 insertions(+), 151 deletions(-)
diff --git a/test_plans/interrupt_pmd_test_plan.rst b/test_plans/interrupt_pmd_test_plan.rst
index 6dfd821..7503283 100644
--- a/test_plans/interrupt_pmd_test_plan.rst
+++ b/test_plans/interrupt_pmd_test_plan.rst
@@ -57,8 +57,8 @@ Iommu pass through feature has been enabled in kernel.
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: PF interrupt pmd with uio
-=====================================
+Test Case1: PF interrupt pmd with different queue
+=================================================
Run l3fwd-power with one queue per port::
l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
@@ -76,51 +76,29 @@ After the packet forwarded, thread on core1 and core 2 will return to sleep.
Send packet flows to Port0 and Port1, check that thread on core1 and core2 will
keep up awake.
-Test Case2: PF interrupt pmd with vfio
-======================================
-Run l3fwd-power with one queue per port::
- l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
+Run l3fwd-power with random number queue per port, if is 4::
+ l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config="0,0,0),(0,1,1),\
+ (0,2,2),(0,3,3),(0,4,4)"
-Send one packet to Port0 and Port1, 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
+Send packet with increased dest IP to Port0, check that all threads waked up
Send packet flows to Port0 and Port1, check that thread on core1 and core2 will
-keep up awake.
-
-Test Case3: PF interrupt pmd multi queue with vfio
-==================================================
-Run l3fwd-power with two queues per port::
- l3fwd-power -c 1f -n 4 -- -p 0x3 \
- --config="(0,0,1),(0,1,2)(1,0,3),(1,1,4)"
+keep up awake.
-Send packet with increased dest IP to Port0 and Port1, check that thread on
-core1,core2,core3,core4 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,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
-
-Check the packet has been normally forwarded.
+Run l3fwd-power with 32 queues per port::
+ l3fwd-power -c ffffffff -n 4 -- -p 0x3 -P --config="(0,0,0),(0,1,1),\
+ (0,2,2),(0,3,3),(0,4,4),(0,5,5),(0,6,6),(0,7,7),(0,8,8),
+ (0,9,9),(0,10,10),(0,11,11),(0,12,12),(0,13,13),(0,14,14),\
+ (0,15,15),\
+ (1,0,16),(1,1,17),(1,2,18),(1,3,19),(1,4,20),(1,5,21),(1,6,22),\
+ (1,7,23),(1,8,24),(1,9,25),(1,10,26),(1,11,27),(1,12,28),\
+ (1,13,29),(1,14,30),\(1,15,31)"
+Send packet with increased dest IP to Port0, check that all threads waked up
-After the packet forwarded, thread on core1,core2,core3,core4 will return to
-sleep.
- 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
+igb_uio driver only ues one queue 0
-Send packet flows to Port0 and Port1, check that thread on core1,core2,core3,
-core4 will keep up awake.
-Test Case4: PF lsc interrupt with vfio
+Test Case2: PF lsc interrupt with vfio
======================================
Run l3fwd-power with one queue per port::
l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
@@ -137,118 +115,8 @@ driver.
Plug in Port1 cable, check that link up interrtup captured and handled by pmd
driver.
-Test Case5: PF interrupt max Rx queues with vfio
-================================================
-Run l3fwd-power with 32 queues per port::
- l3fwd-power -c ffffffff -n 4 -- -p 0x3 -P --config="(0,0,0),(0,1,1),\
- (0,2,2),(0,3,3),(0,4,4),(0,5,5),(0,6,6),(0,7,7),(0,8,8),
- (0,9,9),(0,10,10),(0,11,11),(0,12,12),(0,13,13),(0,14,14),\
- (0,15,15),\
- (1,0,16),(1,1,17),(1,2,18),(1,3,19),(1,4,20),(1,5,21),(1,6,22),\
- (1,7,23),(1,8,24),(1,9,25),(1,10,26),(1,11,27),(1,12,28),\
- (1,13,29),(1,14,30),\(1,15,31)"
-
-Send packet with increased dest IP to Port0, check that all threads waked up:
-
-Test Case6: VF interrupt pmd in VM with uio
-===========================================
-Create one VF per Port in host and add these two VFs into VM:
- rmmod ixgbe
- modprobe ixgbe max_vfs=1
- virsh
- virsh # nodedev-dettach PCI_VF1
- virsh # nodedev-dettach PCI_VF2
-
-Assign mac address for VF:
- ip link set p786p1 vf 0 mac 00:11:22:33:44:55
- ip link set p786p2 vf 0 mac 00:11:22:33:44:66
-
-Start VM and start l3fwd-power with one queue per port in VM:
- l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
-
-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
-
-Send packet flows to VF0 and VF1, check that thread on core1 and core2 will
-keep up awake.
-
-Test Case7: VF interrupt pmd in Host with uio
-=============================================
-Create one VF per Port in host and make sure PF interface up:
- rmmod ixgbe
- modprobe ixgbe max_vfs=1
- ifconfig p786p1 up
- ifconfig p786p2 up
-
-Assign mac address for VF:
- ip link set p786p1 vf 0 mac 00:11:22:33:44:55
- ip link set p786p2 vf 0 mac 00:11:22:33:44:66
-
-Bind VF device to igb_uio:
- ./usertools/dpdk-devbind.py --bind=igb_uio 0000:08:10.0 0000:08:10.1
-
-Start VM and start l3fwd-power with one queue per port in VM:
- l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
-
-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
-
-Send packet flows to VF0 and VF1, check that thread on core1 and core2 will
-keep up awake.
-
-Test Case8: VF interrupt pmd in Host with vfio
-==============================================
-Create one VF per Port in host and make sure PF interface up:
- rmmod ixgbe
- modprobe ixgbe max_vfs=2
- ifconfig p786p1 up
- ifconfig p786p2 up
-
-Assign mac address for VF:
- ip link set p786p1 vf 0 mac 00:11:22:33:44:55
- ip link set p786p2 vf 0 mac 00:11:22:33:44:66
-
-Bind VF device to igb_uio:
- ./usertools/dpdk-devbind.py --bind=igb_uio 0000:08:10.0 0000:08:10.1
-
-Start VM and start l3fwd-power with two queues per port in VM:
- l3fwd-power -c 1f -n 4 -- -p 0x3 -P \
- --config="(0,0,1),(0,1,2)(1,0,3),(1,1,4)"
-
-Send packets with increased dest IP to Port0 and Port1, check that thread on
-core1,core2,core3,core4 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,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
-
-Check the packet has been normally forwarded.
-
-After the packet forwarded, thread on core1,core2,core3,core4 will return to
-sleep.
- 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
-
-Send packet flows to Port0 and Port1, check that thread on core1,core2,core3,
-core4 will keep up awake.
-Test Case9: PF interrupt pmd latency test
+Test Case3: PF interrupt pmd latency test
=========================================
Setup validation scenario the case as test1
Send burst packet flow to Port0 and Port1, use IXIA capture the maxmium
--
1.9.3
next reply other threads:[~2017-06-09 6:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 6:08 xu,gang [this message]
2017-06-14 15:51 ` Liu, Yong
-- strict thread matches above, loose matches on Subject: below --
2017-09-08 2:30 [dts] [PATCH V2] add test suite for vf interruot_pmd xu,gang
2017-09-08 2:30 ` [dts] [PATCH V1] modify the interrupt pmd test plan xu,gang
2017-10-09 11:51 ` Liu, Yong
2017-05-27 2:18 xu,gang
2017-06-09 12:45 ` 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=1496988494-73053-1-git-send-email-gangx.xu@intel.com \
--to=gangx.xu@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).