DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kantecki, Tomasz" <tomasz.kantecki@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] app/test: reduced duration of red_autotest
Date: Wed, 8 Jun 2016 15:56:29 +0000	[thread overview]
Message-ID: <E79CF84CF47B0B42B66F4F5835125F9C8182D3AB@IRSMSX101.ger.corp.intel.com> (raw)
In-Reply-To: <5309764.cBvyyiAfAy@xps13>

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.

Alternatively, one or two more test cases can be removed from the fast_test. A few experiments with this option give me test duration at 5[s] level. I guess this too much off from the 1[s] target.

Regards,
Tomasz


--------------------------------------------------------------
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.

  parent reply	other threads:[~2016-06-08 15:56 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 [this message]
2016-06-08 16:22     ` Thomas Monjalon
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=E79CF84CF47B0B42B66F4F5835125F9C8182D3AB@IRSMSX101.ger.corp.intel.com \
    --to=tomasz.kantecki@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).