From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 171893DC for ; Wed, 6 Sep 2017 08:16:29 +0200 (CEST) Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Sep 2017 23:16:29 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,482,1498546800"; d="scan'208";a="145953545" Received: from dpdk-test32.sh.intel.com (HELO [10.67.119.120]) ([10.67.119.120]) by orsmga005.jf.intel.com with ESMTP; 05 Sep 2017 23:16:28 -0700 Message-ID: <59B00D55.3050501@intel.com> Date: Wed, 06 Sep 2017 22:59:33 +0800 From: "Liu, Yong" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "Xu, Qian Q" , "Xu, HuilongX" , "dts@dpdk.org" References: <1503646931-91671-1-git-send-email-huilongx.xu@intel.com> <82F45D86ADE5454A95A89742C8D1410E3B7624C0@shsmsx102.ccr.corp.intel.com> In-Reply-To: <82F45D86ADE5454A95A89742C8D1410E3B7624C0@shsmsx102.ccr.corp.intel.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dts] [PATCH V1 1/6] add a new config file for fortvill PF full function test 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: , X-List-Received-Date: Wed, 06 Sep 2017 06:16:30 -0000 Qian, I'm wondering who will take the ownership of execution plan. If there's one new suite like generic_flow, it should be added into one or more execution cfg. Who will do that? And current only Fortville has its specified execution plan, how about other types of NICs like Niantic? By now only three suites are added to performance execution plan, the coverage is not enough. To solve all those kinds of problem should need one kind of infrastructure to handle the execution plan. Thanks, Marvin On 09/06/2017 01:07 PM, Xu, Qian Q wrote: > Hi, Marvin > Do you have comments on this? > >> -----Original Message----- >> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of xu,huilong >> Sent: Friday, August 25, 2017 3:42 PM >> To: dts@dpdk.org >> Cc: Xu, HuilongX >> Subject: [dts] [PATCH V1 1/6] add a new config file for fortvill PF full function >> test >> >> Signed-off-by: xu,huilong >> --- >> executions/execution_fortville_full.cfg | 60 >> +++++++++++++++++++++++++++++++++ >> 1 file changed, 60 insertions(+) >> create mode 100644 executions/execution_fortville_full.cfg >> >> diff --git a/executions/execution_fortville_full.cfg >> b/executions/execution_fortville_full.cfg >> new file mode 100644 >> index 0000000..0d3a4b7 >> --- /dev/null >> +++ b/executions/execution_fortville_full.cfg >> @@ -0,0 +1,60 @@ >> +[Execution1] >> +crbs= >> +drivername= rx_mode=full >> +test_suites= >> + blacklist, >> + checksum_offload, >> + cmdline, >> + coremask, >> + distributor, >> + dual_vlan, >> + dynamic_config, >> + efd, >> + external_mempool_handler, >> + fdir, >> + fortville_rss_granularity_config, >> + generic_filter, >> + hello_world, >> + hot_plug, >> + ieee1588, >> + ipfrag, >> + ipgre, >> + ipv4_reassembly, >> + jumboframes, >> + keep_alive, >> + kni, >> + l2fwd, >> + link_flowctrl, >> + link_status_interrupt, >> + mac_filter, >> + mempool_exthandler, >> + multiprocess, >> + netmap_compat, >> + nvgre, >> + pmd, >> + pmd_bonded, >> + pmdpcap, >> + pmdrss_hash, >> + pmdrssreta, >> + ptpclient, >> + ptype_mapping, >> + qinq_filter, >> + queue_start_stop, >> + quota_watermark, >> + rxtx_callbacks, >> + scatter, >> + short_live, >> + shutdown_api, >> + skeleton, >> + timer, >> + tso, >> + tx_preparation, >> + uni_pkt, >> + userspace_ethtool, >> + vlan, >> + vlan_ethertype_config, >> + vxlan >> +targets= >> + x86_64-native-linuxapp-gcc >> +parameters=nic_type=cfg:func=true >> -- >> 1.9.3