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 414EDA0613 for ; Wed, 28 Aug 2019 12:16:03 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0024A1DBD; Wed, 28 Aug 2019 12:16:02 +0200 (CEST) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by dpdk.org (Postfix) with ESMTP id 5EEF01DB9 for ; Wed, 28 Aug 2019 12:16:01 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga104.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Aug 2019 03:16:00 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,440,1559545200"; d="scan'208";a="174869000" Received: from fmsmsx108.amr.corp.intel.com ([10.18.124.206]) by orsmga008.jf.intel.com with ESMTP; 28 Aug 2019 03:16:00 -0700 Received: from FMSMSX109.amr.corp.intel.com (10.18.116.9) by FMSMSX108.amr.corp.intel.com (10.18.124.206) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 28 Aug 2019 03:15:59 -0700 Received: from shsmsx102.ccr.corp.intel.com (10.239.4.154) by fmsmsx109.amr.corp.intel.com (10.18.116.9) with Microsoft SMTP Server (TLS) id 14.3.439.0; Wed, 28 Aug 2019 03:15:59 -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; Wed, 28 Aug 2019 18:15:57 +0800 From: "Tu, Lijuan" To: "Wu, ChangqingX" , "dts@dpdk.org" CC: "Wu, ChangqingX" Thread-Topic: [dts] [PATCH V1] test_plans/interrupt:change queue for different nic Thread-Index: AQHVVBl+jxn/k+8rwk6DQ7/ZOSQJQ6cQatVg Date: Wed, 28 Aug 2019 10:15:56 +0000 Message-ID: <8CE3E05A3F976642AAB0F4675D0AD20E0BB06B11@SHSMSX101.ccr.corp.intel.com> References: <1565949892-112878-1-git-send-email-changqingx.wu@intel.com> In-Reply-To: <1565949892-112878-1-git-send-email-changqingx.wu@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.2.0.6 dlp-reaction: no-action x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMzQzMWM1NmEtZDJlYy00ZmVlLTljZDItNTdjMTljMzEwMzVhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiS0E1bmt4M0JPN2JWZTdDR05vWThZdGV5K21GaFdYMVJoNXlvdFl2MWpBRkhvUmpkZjdUQ29XenJpTkZlZWw2SCJ9 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" > -----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 different= nic >=20 > Beautify format and change queue distribution for different nic >=20 > Signed-off-by: changqingxwu > --- > test_plans/interrupt_pmd_test_plan.rst | 32 +++++++++++--------------- > 1 file changed, 13 insertions(+), 19 deletions(-) >=20 > 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 0000:08:10.0, > 0000:08:10.1. >=20 > Iommu pass through feature has been enabled in kernel:: >=20 > - intel_iommu=3Don iommu=3Dpt > + intel_iommu=3Don iommu=3Dpt >=20 > Support igb_uio and vfio driver, if used vfio, kernel need 3.6+ and enab= le 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 >=20 > Run l3fwd-power with one queue per port:: >=20 > - 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)" >=20 > Send one packet to Port0 and Port1, check that thread on core1 and core2 > waked up:: >=20 > - > - 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 >=20 > Check the packet has been normally forwarded. >=20 > After the packet forwarded, thread on core1 and core 2 will return to sl= eep:: >=20 > - > - 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 >=20 > Send packet flows to Port0 and Port1, check that thread on core1 and cor= e2 > will keep up awake. >=20 > Run l3fwd-power with random number queue per port, if is 4:: >=20 > - 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)" >=20 > Send packet with increased dest IP to Port0, check that all threads wake= d up >=20 > Send packet flows to Port0 and Port1, check that thread on core1 and cor= e2 > will keep up awake. >=20 > -Run l3fwd-power with 32 queues per port:: > +Run l3fwd-power with 15 queues per port:: [Lijuan] why reduce queues from 32 to 15 ? >=20 > - 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) >=20 > Send packet with increased dest IP to Port0, check that all threads wake= d up >=20 > @@ -115,7 +109,7 @@ Test Case2: PF lsc interrupt with vfio >=20 > Run l3fwd-power with one queue per port:: >=20 > - 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)" >=20 > Plug out Port0 cable, check that link down interrupt captured and handle= d > by pmd driver. > -- > 2.17.2