From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id F0FEFA0613 for ; Thu, 29 Aug 2019 05:41:19 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DA31E1BF84; Thu, 29 Aug 2019 05:41:19 +0200 (CEST) Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 163C61BF81 for ; Thu, 29 Aug 2019 05:41:17 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Aug 2019 20:41:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,442,1559545200"; d="scan'208";a="182218221" Received: from fmsmsx105.amr.corp.intel.com ([10.18.124.203]) by fmsmga007.fm.intel.com with ESMTP; 28 Aug 2019 20:41:16 -0700 Received: from fmsmsx120.amr.corp.intel.com (10.18.124.208) by FMSMSX105.amr.corp.intel.com (10.18.124.203) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 28 Aug 2019 20:41:16 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by fmsmsx120.amr.corp.intel.com (10.18.124.208) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 28 Aug 2019 20:41:16 -0700 Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.80]) by shsmsx102.ccr.corp.intel.com ([169.254.2.19]) with mapi id 14.03.0439.000; Thu, 29 Aug 2019 11:41:14 +0800 From: "Wu, ChangqingX" To: "Tu, Lijuan" , "dts@dpdk.org" CC: "Zhang, Yuwei1" Thread-Topic: [dts] [PATCH V1] test_plans/interrupt:change queue for different nic Thread-Index: AQHVXYmV2eHWSRyFT0CzB56IygGhoKcRY1Vw//+C7oCAAJWMkA== Date: Thu, 29 Aug 2019 03:41:14 +0000 Message-ID: <7F81DD3887C58F49A6B2EFEC3C28E22E0B747C19@SHSMSX101.ccr.corp.intel.com> References: <1565949892-112878-1-git-send-email-changqingx.wu@intel.com> <8CE3E05A3F976642AAB0F4675D0AD20E0BB06B11@SHSMSX101.ccr.corp.intel.com> <7F81DD3887C58F49A6B2EFEC3C28E22E0B747A75@SHSMSX101.ccr.corp.intel.com> <8CE3E05A3F976642AAB0F4675D0AD20E0BB07163@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <8CE3E05A3F976642AAB0F4675D0AD20E0BB07163@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH V1] test_plans/interrupt:change queue for different nic X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" Thanks for your suggest, I will take it. -----Original Message----- From: Tu, Lijuan=20 Sent: Thursday, August 29, 2019 10:45 AM To: Wu, ChangqingX ; dts@dpdk.org Cc: Zhang, Yuwei1 Subject: RE: [dts] [PATCH V1] test_plans/interrupt:change queue for differe= nt nic I think the test plan should be generic, NOT specific for some NICs unless = it is designed for some NICS.=20 If you found some NIC limitation, I suggest, you can add a note in test pla= n. I think , not only Niantic support this POWER feature, also Fortville , and= in future, maybe more NICS. > -----Original Message----- > From: Wu, ChangqingX > Sent: Thursday, August 29, 2019 10:14 AM > To: Tu, Lijuan ; dts@dpdk.org > Cc: Zhang, Yuwei1 > Subject: RE: [dts] [PATCH V1] test_plans/interrupt:change queue for=20 > different nic >=20 > niantic net card not supports more than 15 queues by testing >=20 > -----Original Message----- > From: Tu, Lijuan > Sent: Wednesday, August 28, 2019 6:16 PM > To: Wu, ChangqingX ; dts@dpdk.org > Cc: Wu, ChangqingX > Subject: RE: [dts] [PATCH V1] test_plans/interrupt:change queue for=20 > different nic >=20 >=20 >=20 > > -----Original Message----- > > From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of changqingxwu > > Sent: Friday, August 16, 2019 6:05 PM > > To: dts@dpdk.org > > Cc: Wu, ChangqingX > > Subject: [dts] [PATCH V1] test_plans/interrupt:change queue for=20 > > different nic > > > > Beautify format and change queue distribution for different nic > > > > Signed-off-by: changqingxwu > > --- > > 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..f30951e 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=20 > > 0000:08:10.0, 0000:08:10.1. > > > > Iommu pass through feature has been enabled in kernel:: > > > > - intel_iommu=3Don iommu=3Dpt > > + intel_iommu=3Don iommu=3Dpt > > > > Support igb_uio and vfio driver, if used vfio, kernel need 3.6+ and=20 > > enable vt- d in bios. When used vfio, requested to insmod two=20 > > drivers vfio > and vfio-pci. > > @@ -65,45 +65,39 @@ Test Case1: PF interrupt pmd with different=20 > > queue > > > > Run l3fwd-power with one queue per port:: > > > > - l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config=3D"(0,0,1),(1,0,2)" > > + l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config=3D"(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=20 > > + port1,rxq0 > > > > Check the packet has been normally forwarded. > > > > After the packet forwarded, thread on core1 and core 2 will return=20 > > 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=20 > > + triggers > > > > Send packet flows to Port0 and Port1, check that thread on core1=20 > > 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=3D"0,0,0),(0,1,1),= \ > > - (0,2,2),(0,3,3),(0,4,4)" > > + l3fwd-power -c 0x3f -n 4 -- -p 0x3 -P --config=3D"(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=20 > > waked up > > > > Send packet flows to Port0 and Port1, check that thread on core1=20 > > and > > core2 will keep up awake. > > > > -Run l3fwd-power with 32 queues per port:: > > +Run l3fwd-power with 15 queues per port:: > [Lijuan] why reduce queues from 32 to 15 ? > > > > - l3fwd-power -c ffffffff -n 4 -- -p 0x3 -P --config=3D"(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 ffffff -n 4 -- -p 0x3 -P --config=3D"(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=20 > > 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=3D"(0,0,1),(1,0,2)" > > + l3fwd-power -c 7 -n 4 -- -p 0x3 -P --config=3D"(0,0,1),(1,0,2)" > > > > Plug out Port0 cable, check that link down interrupt captured and=20 > > handled by pmd driver. > > -- > > 2.17.2