From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Kantecki, Tomasz" <tomasz.kantecki@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] app/test: reduced duration of red_autotest
Date: Wed, 08 Jun 2016 18:22:52 +0200 [thread overview]
Message-ID: <2506582.jAQRcmA1gs@xps13> (raw)
In-Reply-To: <E79CF84CF47B0B42B66F4F5835125F9C8182D3AB@IRSMSX101.ger.corp.intel.com>
2016-06-08 15:56, Kantecki, Tomasz:
> Hi Thomas,
>
> > > 12s is long for a functional test. We are used to have tests of less than 1s.
> > > Do you think this magnitude order can be achieved for red tests?
> >
> > This is a real challenge :) Let me take another look into it.
>
> I had a 2nd look into this test suite and reducing time for functional tests is doable but labor intensive. Let me explain:
> RED/WRED algorithm is time based (packet queue events in time). For tracking time the test uses TSC (x86 time stamp counter). This could be replaced with some fake time stamp in functional tests and result in significant reduction of execution time. It needs couple of days to carefully replace TSC with a fake time stamp solution without breaking test logic.
Sorry, I haven't dived into the code, but I don't understand how we get
some seconds delays in a code for fast processing on nano-second CPU.
Are you sure you cannot have the same result with less iterations and
shorter timeouts?
next prev parent reply other threads:[~2016-06-08 16:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-07 13:49 Tomasz Kantecki
2016-06-07 14:03 ` Thomas Monjalon
2016-06-07 15:12 ` Kantecki, Tomasz
2016-06-08 15:56 ` Kantecki, Tomasz
2016-06-08 16:22 ` Thomas Monjalon [this message]
2016-06-09 10:31 ` [dpdk-dev] [PATCH v2] " Tomasz Kantecki
2016-06-13 10:26 ` [dpdk-dev] [PATCH v3] " Tomasz Kantecki
2016-06-13 19:52 ` 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=2506582.jAQRcmA1gs@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=tomasz.kantecki@intel.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).