From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 80CD7374C for ; Tue, 24 May 2016 19:08:21 +0200 (CEST) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 24 May 2016 10:08:19 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,360,1459839600"; d="scan'208";a="987827790" Received: from irsmsx154.ger.corp.intel.com ([163.33.192.96]) by fmsmga002.fm.intel.com with ESMTP; 24 May 2016 10:08:18 -0700 Received: from irsmsx108.ger.corp.intel.com ([169.254.11.33]) by IRSMSX154.ger.corp.intel.com ([169.254.12.18]) with mapi id 14.03.0248.002; Tue, 24 May 2016 18:08:16 +0100 From: "Dumitrescu, Cristian" To: Thomas Monjalon , "Kantecki, Tomasz" CC: "dev@dpdk.org" Thread-Topic: fast red autotest Thread-Index: AQHRq1kox96HbArBm0yRkujf3+6jo5+zhQrwgBSz+YCAACwyQA== Date: Tue, 24 May 2016 17:08:15 +0000 Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126479EC622@IRSMSX108.ger.corp.intel.com> References: <2017180.gcuZq2Skul@xps13> <3EB4FA525960D640B5BDFFD6A3D89126479BB2F8@IRSMSX108.ger.corp.intel.com> <3881475.Zgz2Wz8CD9@xps13> In-Reply-To: <3881475.Zgz2Wz8CD9@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDA0YWJiYWUtYjdjMy00ZWIzLThjNGYtMmIxYmMwNDhjZjJmIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6InRMa0p5Y2xlMVwvaDR0bks0VU5GZFpwZUZ3V2hWRE1HNElVWTYxNkhtcUtnPSJ9 x-ctpclassification: CTP_IC x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] fast red autotest X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2016 17:08:22 -0000 Hi Thomas, >>From my side, I am OK to remove RED from the fast autotest, as long as it i= s kept available as part of the normal/full autotest of DPDK. Some of the RED autotests need a long time to run in order to train the his= tory for the average queue size stochastic variable, therefore it is diffic= ult to shorten them. However, some tests are quick to execute, so those tes= ts can still be included into the fast autotest. Tomazs, any comments/propo= sal? Regards, Cristian > -----Original Message----- > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > Sent: Tuesday, May 24, 2016 4:24 PM > To: Dumitrescu, Cristian ; Kantecki, Tomas= z > > Cc: dev@dpdk.org > Subject: Re: fast red autotest >=20 > Any news Tomasz, Cristian? >=20 > 2016-05-11 10:15, Dumitrescu, Cristian: > > CC-ing Tomasz, who is the original author of RED implementation and its > autotest. Tomasz, what do you think? > > > > > -----Original Message----- > > > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com] > > > Sent: Wednesday, May 11, 2016 8:45 AM > > > To: Dumitrescu, Cristian > > > Cc: dev@dpdk.org > > > Subject: fast red autotest > > > > > > The autotest for librte_sched red takes more than a minute. > > > Would it be possible to reduce it to a second please? > > > If it is really impossible, it must be removed from fast_test. >=20