From: Song Jiale <songx.jiale@intel.com>
To: dts@dpdk.org
Cc: Song Jiale <songx.jiale@intel.com>
Subject: [dts] [PATCH V1 2/2] test_plans/*interrupt_pmd: transfer test cases
Date: Fri, 13 Jan 2023 13:50:15 +0000 [thread overview]
Message-ID: <20230113135015.1317296-2-songx.jiale@intel.com> (raw)
In-Reply-To: <20230113135015.1317296-1-songx.jiale@intel.com>
transfer pf cases from vf_interrupt_pmd suite to interrupt_pmd suite.
cases list:
test_nic_interrupt_PF_vfio_pci
test_nic_interrupt_PF_igb_uio
Signed-off-by: Song Jiale <songx.jiale@intel.com>
---
test_plans/interrupt_pmd_test_plan.rst | 52 +++++++++++++++++----
test_plans/vf_interrupt_pmd_test_plan.rst | 56 ++---------------------
2 files changed, 48 insertions(+), 60 deletions(-)
diff --git a/test_plans/interrupt_pmd_test_plan.rst b/test_plans/interrupt_pmd_test_plan.rst
index d812ad0c..38ee79d2 100644
--- a/test_plans/interrupt_pmd_test_plan.rst
+++ b/test_plans/interrupt_pmd_test_plan.rst
@@ -104,16 +104,50 @@ driver.
Plug in Port1 cable, check that link up interrupt captured and handled by pmd
driver.
+Test Case3: Check Interrupt for PF with vfio driver on ixgbe and i40e
+=====================================================================
-Test Case3: PF interrupt pmd latency test
-=========================================
+1. Bind NIC PF to vfio-pci drvier::
-Setup validation scenario the case as test1
-Send burst packet flow to Port0 and Port1, use IXIA capture the maximum
-latency.
+ modprobe vfio-pci;
-Compare latency(l3fwd-power PF interrupt pmd with uio) with l3fwd latency.
+ ./usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:00.0
+
+2. start l3fwd-power with PF::
+
+ ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 1-4 -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::
+
+ sendp([Ether(dst='pf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')], iface="tester_intf")
+
+ 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: lcore 2 sleeps until interrupt triggers
+
+Test Case4: Check Interrupt for PF with igb_uio driver on ixgbe and i40e
+========================================================================
+
+1. Bind NIC PF to igb_uio drvier::
+
+ modprobe uio;
+ insmod x86_64-native-linuxapp-gcc/kmod/igb_uio.ko;
+
+ ./usertools/dpdk-devbind.py --bind=igb_uio 0000:04:00.0
+
+2. start l3fwd-power with PF::
+
+ ./x86_64-native-linuxapp-gcc/examples/dpdk-l3fwd-power -l 1-4 -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::
+
+ sendp([Ether(dst='pf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')], iface="tester_intf")
+
+ 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: lcore 2 sleeps until interrupt triggers
-Setup validation scenario the case as test2
-Send burst packet flow to Port0 and Port1, use IXIA capture the maximum
-latency.
diff --git a/test_plans/vf_interrupt_pmd_test_plan.rst b/test_plans/vf_interrupt_pmd_test_plan.rst
index b7cdeb3e..910b5ee7 100644
--- a/test_plans/vf_interrupt_pmd_test_plan.rst
+++ b/test_plans/vf_interrupt_pmd_test_plan.rst
@@ -39,54 +39,7 @@ Modify the DPDK-l3fwd-power source code and recompile the l3fwd-power::
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: Check Interrupt for PF with vfio driver on ixgbe and i40e
-=====================================================================
-
-1. Bind NIC PF to vfio-pci drvier::
-
- modprobe vfio-pci;
-
- ./usertools/dpdk-devbind.py --bind=vfio-pci 0000:04:00.0
-
-2. start l3fwd-power with PF::
-
- ./x86_64-native-linuxapp-gcc/examples/dpdk-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::
-
- sendp([Ether(dst='pf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')], iface="tester_intf")
-
- 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: lcore 2 sleeps until interrupt triggers
-
-Test Case2: Check Interrupt for PF with igb_uio driver on ixgbe and i40e
-========================================================================
-
-1. Bind NIC PF to igb_uio drvier::
-
- modprobe uio;
- insmod x86_64-native-linuxapp-gcc/kmod/igb_uio.ko;
-
- ./usertools/dpdk-devbind.py --bind=igb_uio 0000:04:00.0
-
-2. start l3fwd-power with PF::
-
- ./x86_64-native-linuxapp-gcc/examples/dpdk-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::
-
- sendp([Ether(dst='pf_mac')/IP()/UDP()/Raw(load='XXXXXXXXXXXXXXXXXX')], iface="tester_intf")
-
- 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: lcore 2 sleeps until interrupt triggers
-
-Test Case3: Check Interrupt for VF with vfio driver on ixgbe and i40e
+Test Case1: Check Interrupt for VF with vfio driver on ixgbe and i40e
=====================================================================
1. Generate NIC VF, then bind it to vfio drvier::
@@ -112,7 +65,7 @@ Test Case3: Check Interrupt for VF with vfio driver on ixgbe and i40e
L3FWD_POWER: lcore 2 sleeps until interrupt triggers
-Test Case4: VF interrupt pmd in VM with vfio-pci
+Test Case2: VF interrupt pmd in VM with vfio-pci
================================================
1. Generate NIC VF, then bind it to vfio drvier::
@@ -160,7 +113,7 @@ Test Case4: VF interrupt pmd in VM with vfio-pci
L3FWD_POWER: lcore 2 sleeps until interrupt triggers
-Test Case5: vf multi-queue interrupt with vfio-pci on i40e
+Test Case3: vf multi-queue interrupt with vfio-pci on i40e
==========================================================
1. Generate NIC VF, then bind it to vfio drvier::
@@ -187,7 +140,7 @@ Test Case5: vf multi-queue interrupt with vfio-pci on i40e
L3FWD_POWER: lcore 3 is waked up from rx interrupt on port 0 queue 2
L3FWD_POWER: lcore 4 is waked up from rx interrupt on port 0 queue 3
-Test Case6: VF multi-queue interrupt in VM with vfio-pci on i40e
+Test Case4: VF multi-queue interrupt in VM with vfio-pci on i40e
================================================================
1. Generate NIC VF, then bind it to vfio drvier::
@@ -233,3 +186,4 @@ Test Case6: VF multi-queue interrupt in VM with vfio-pci on i40e
L3FWD_POWER: lcore 1 is waked up from rx interrupt on port 0 queue 1
L3FWD_POWER: lcore 2 is waked up from rx interrupt on port 0 queue 2
L3FWD_POWER: lcore 3 is waked up from rx interrupt on port 0 queue 3
+
--
2.25.1
next prev parent reply other threads:[~2023-01-13 5:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-13 13:50 [dts] [PATCH V1 1/2] tests/*interrupt_pmd: " Song Jiale
2023-01-13 13:50 ` Song Jiale [this message]
2023-01-13 8:17 ` [dts] [PATCH V1 2/2] test_plans/*interrupt_pmd: " lijuan.tu
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=20230113135015.1317296-2-songx.jiale@intel.com \
--to=songx.jiale@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).