From: "Kantecki, Tomasz" <tomasz.kantecki@intel.com>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] fast red autotest
Date: Wed, 25 May 2016 11:06:10 +0000 [thread overview]
Message-ID: <E79CF84CF47B0B42B66F4F5835125F9C8181AECF@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D89126479EC622@IRSMSX108.ger.corp.intel.com>
Hi Thomas,
I had a quick look through these tests and it will need some effort to rework them to run in shorter time.
I agree to remove this suite from the fast_test as long as it gets exercised in other test paths.
Regards,
Tomasz
> -----Original Message-----
> From: Dumitrescu, Cristian
> Sent: Tuesday, May 24, 2016 6:08 PM
> To: Thomas Monjalon <thomas.monjalon@6wind.com>; Kantecki, Tomasz
> <tomasz.kantecki@intel.com>
> Cc: dev@dpdk.org
> Subject: RE: fast red autotest
>
> Hi Thomas,
>
> From my side, I am OK to remove RED from the fast autotest, as long as it is
> 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
> history for the average queue size stochastic variable, therefore it is difficult
> to shorten them. However, some tests are quick to execute, so those tests
> can still be included into the fast autotest. Tomazs, any comments/proposal?
>
> Regards,
> Cristian
>
> > -----Original Message-----
> > From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]
> > Sent: Tuesday, May 24, 2016 4:24 PM
> > To: Dumitrescu, Cristian <cristian.dumitrescu@intel.com>; Kantecki,
> > Tomasz <tomasz.kantecki@intel.com>
> > Cc: dev@dpdk.org
> > Subject: Re: fast red autotest
> >
> > Any news Tomasz, Cristian?
> >
> > 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 <cristian.dumitrescu@intel.com>
> > > > 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.
> >
--------------------------------------------------------------
Intel Research and Development Ireland Limited
Registered in Ireland
Registered Office: Collinstown Industrial Park, Leixlip, County Kildare
Registered Number: 308263
This e-mail and any attachments may contain confidential material for the sole
use of the intended recipient(s). Any review or distribution by others is
strictly prohibited. If you are not the intended recipient, please contact the
sender and delete all copies.
next prev parent reply other threads:[~2016-05-25 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-11 7:45 Thomas Monjalon
2016-05-11 10:15 ` Dumitrescu, Cristian
2016-05-24 15:23 ` Thomas Monjalon
2016-05-24 17:08 ` Dumitrescu, Cristian
2016-05-25 11:06 ` Kantecki, Tomasz [this message]
2016-05-25 11:41 ` Thomas Monjalon
2016-05-27 14:04 ` Kantecki, Tomasz
2016-05-27 14:42 ` Thomas Monjalon
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=E79CF84CF47B0B42B66F4F5835125F9C8181AECF@IRSMSX101.ger.corp.intel.com \
--to=tomasz.kantecki@intel.com \
--cc=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.com \
/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).