From: "Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>
To: "Pattan, Reshma" <reshma.pattan@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, 22 Oct 2018 07:43:08 +0000 [thread overview]
Message-ID: <7AE31235A30B41498D1C31348DC858BD5B4D8F29@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <3AEA2BF9852C6F48A459DA490692831F2A3B6F7E@irsmsx110.ger.corp.intel.com>
Hi Reshma,
>-----Original Message-----
>From: Pattan, Reshma
>Sent: Wednesday, October 10, 2018 9:54 PM
>To: Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>;
>dev@dpdk.org
>Cc: rsanford@akamai.com
>Subject: RE: [PATCH] test: reduce duration for timer autotest
>
>Hi
>
>> -----Original Message-----
>> From: Parthasarathy, JananeeX M
>> Sent: Saturday, September 22, 2018 12:55 PM
>> To: dev@dpdk.org
>> Cc: Pattan, Reshma <reshma.pattan@intel.com>; rsanford@akamai.com;
>> Parthasarathy, JananeeX M <jananeex.m.parthasarathy@intel.com>
>> Subject: [PATCH] test: reduce duration for timer autotest
>>
>>
>> /* pick random timer to reset, stopping them first half the time */
>> - for (i = 0; i < 100000; i++) {
>> + for (i = 0; i < NB_STRESS2_TIMERS; i++) {
>
>Just reduce the iteration to some number, instead of using macro
>NB_STRESS2_TIMERS, which seem to be specific for number of timers.
>
>(Or) can this test be considered as perf ? and ignore above changes.?
>
>Any one any comments?
>
>Thanks,
>Reshma
>
NB_STRESS2_TIMERS is used for all iterations in the test and timer structure is allocated NB_STRESS2_TIMERS only, hence used the same.
This seems to be stress test so better to be considered as perf test and no changes are required.
Please let us know about it.
Regards
MP.Jananee
--------------------------------------------------------------
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:[~2018-10-22 7:43 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 [this message]
2018-10-24 12:21 ` Pattan, Reshma
2018-11-05 16:04 ` Pattan, Reshma
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=7AE31235A30B41498D1C31348DC858BD5B4D8F29@IRSMSX103.ger.corp.intel.com \
--to=jananeex.m.parthasarathy@intel.com \
--cc=dev@dpdk.org \
--cc=reshma.pattan@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).