From: "Zhang, Yuwei1" <yuwei1.zhang@intel.com>
To: "Wu, ChangqingX" <changqingx.wu@intel.com>,
"dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V4] test_plans/interrupt:change queue for different nic
Date: Wed, 4 Sep 2019 07:16:24 +0000 [thread overview]
Message-ID: <EC241D52C34C9A4BA57BFACAB76C70A43D77090B@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1567562912-136353-1-git-send-email-changqingx.wu@intel.com>
Acked-by: Yuwei Zhang
-----Original Message-----
From: Wu, ChangqingX
Sent: Wednesday, September 4, 2019 10:09 AM
To: dts@dpdk.org
Cc: Zhang, Yuwei1 <yuwei1.zhang@intel.com>; Wu, ChangqingX <changqingx.wu@intel.com>
Subject: [dts][PATCH V4] test_plans/interrupt:change queue for different nic
Beautify format, niantic net card not supports more than 15 queues, and need specify drivername is vfio-pci
Signed-off-by: changqingxwu <changqingx.wu@intel.com>
---
test_plans/interrupt_pmd_test_plan.rst | 32 +++++++++++---------------
1 file changed, 13 insertions(+), 19 deletions(-)
diff --git a/test_plans/interrupt_pmd_test_plan.rst b/test_plans/interrupt_pmd_test_plan.rst
index 8834e5f..0ffc818 100644
--- a/test_plans/interrupt_pmd_test_plan.rst
+++ b/test_plans/interrupt_pmd_test_plan.rst
@@ -55,7 +55,7 @@ Assume generated VF PCI address will be 0000:08:10.0, 0000:08:10.1.
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.
@@ -65,45 +65,39 @@ 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)"
+ l3fwd-power -c 0x7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
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
+ 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
+ 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 Port0 and Port1, check that thread on core1 and core2 will keep up awake.
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)"
+ l3fwd-power -c 0x7 -n 4 -- -p 0x3 -P --config="0,0,0),(0,1,1),\
+ (0,2,2),(0,3,3),(0,4,4)"
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.
-Run l3fwd-power with 32 queues per port::
+Run l3fwd-power with 15 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)"
+ l3fwd-power -c 0xffffff -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),(1,0,8),\
+ (1,1,9),(1,2,10),(1,3,11),(1,4,12),(1,5,13),(1,6,14)"
Send packet with increased dest IP to Port0, check that all threads waked up
@@ -115,7 +109,7 @@ 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)"
+ l3fwd-power -c 0x7 -n 4 -- -p 0x3 -P --config="(0,0,1),(1,0,2)"
Plug out Port0 cable, check that link down interrupt captured and handled by pmd driver.
--
2.17.2
next prev parent reply other threads:[~2019-09-04 7:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-04 2:08 changqingxwu
2019-09-04 7:16 ` Zhang, Yuwei1 [this message]
2019-09-12 7:13 ` Tu, Lijuan
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=EC241D52C34C9A4BA57BFACAB76C70A43D77090B@shsmsx102.ccr.corp.intel.com \
--to=yuwei1.zhang@intel.com \
--cc=changqingx.wu@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).