DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Pattan, Reshma" <reshma.pattan@intel.com>
To: "Pattan, Reshma" <reshma.pattan@intel.com>,
	"Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "rsanford@akamai.com" <rsanford@akamai.com>
Subject: Re: [dpdk-dev] [PATCH] test: reduce duration for timer autotest
Date: Mon, 5 Nov 2018 16:04:22 +0000	[thread overview]
Message-ID: <3AEA2BF9852C6F48A459DA490692831F2A3D096F@irsmsx110.ger.corp.intel.com> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F2A3B6F7E@irsmsx110.ger.corp.intel.com>



> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Pattan, Reshma
> Sent: Wednesday, October 10, 2018 5:24 PM
> To: Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>;
> dev@dpdk.org
> Cc: rsanford@akamai.com
> Subject: Re: [dpdk-dev] [PATCH] test: reduce duration for timer autotest
> 
> Hi
> 
> > -----Original Message-----
> > From: Parthasarathy, JananeeX M

When test was ran with reasonable number of lcores ex: 16 the test time is within targeted value of 10sec.
Without specifying the core limit test will run on all available cores and can take longer time. 

So this patch can be Nacked now as expected timings are achieved by limiting the number of cores.


Nacked-by: Reshma Pattan <reshma.pattan@intel.com>

      parent reply	other threads:[~2018-11-05 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-22 11:55 Jananee Parthasarathy
2018-10-10 16:24 ` Pattan, Reshma
2018-10-22  7:43   ` Parthasarathy, JananeeX M
2018-10-24 12:21     ` Pattan, Reshma
2018-11-05 16:04   ` Pattan, Reshma [this message]

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=3AEA2BF9852C6F48A459DA490692831F2A3D096F@irsmsx110.ger.corp.intel.com \
    --to=reshma.pattan@intel.com \
    --cc=dev@dpdk.org \
    --cc=jananeex.m.parthasarathy@intel.com \
    --cc=rsanford@akamai.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).