From: "Wang, Yipeng1" <yipeng1.wang@intel.com>
To: "Parthasarathy, JananeeX M" <jananeex.m.parthasarathy@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Richardson, Bruce" <bruce.richardson@intel.com>,
"De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>,
"Pattan, Reshma" <reshma.pattan@intel.com>,
"Somarowthu, Naga SureshX" <naga.sureshx.somarowthu@intel.com>,
"Gobriel, Sameh" <sameh.gobriel@intel.com>
Subject: Re: [dpdk-dev] [PATCH] test: reduce test time for hash multiwriter ut
Date: Sat, 29 Sep 2018 00:12:34 +0000 [thread overview]
Message-ID: <D2C4A16CA39F7F4E8E384D204491D7A6614E967B@FMSMSX151.amr.corp.intel.com> (raw)
In-Reply-To: <1538030468-21942-1-git-send-email-jananeex.m.parthasarathy@intel.com>
>-----Original Message-----
>From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jananee Parthasarathy
>Sent: Wednesday, September 26, 2018 11:41 PM
>To: dev@dpdk.org
>Cc: Richardson, Bruce <bruce.richardson@intel.com>; De Lara Guarch, Pablo <pablo.de.lara.guarch@intel.com>; Pattan, Reshma
><reshma.pattan@intel.com>; Somarowthu, Naga SureshX <naga.sureshx.somarowthu@intel.com>
>Subject: [dpdk-dev] [PATCH] test: reduce test time for hash multiwriter ut
>
>From: Naga Suresh Somarowthu <naga.sureshx.somarowthu@intel.com>
>
>Reduced test duration for hash_multiwriter_autotest.
>Number of entries and total insertions are reduced
>such that the duration is less than 10 seconds.
>
>Signed-off-by: Naga Suresh Somarowthu <naga.sureshx.somarowthu@intel.com>
>---
> test/test/test_hash_multiwriter.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/test/test/test_hash_multiwriter.c b/test/test/test_hash_multiwriter.c
>index 6a3eb10bd..04b7c18ff 100644
>--- a/test/test/test_hash_multiwriter.c
>+++ b/test/test/test_hash_multiwriter.c
>@@ -38,8 +38,8 @@ struct {
> struct rte_hash *h;
> } tbl_multiwriter_test_params;
>
>-const uint32_t nb_entries = 16*1024*1024;
>-const uint32_t nb_total_tsx_insertion = 15*1024*1024;
>+const uint32_t nb_entries = 5*1024*1024;
>+const uint32_t nb_total_tsx_insertion = 4*1024*1024;
[Wang, Yipeng]
Maybe use 4.5*1024*1024 for nb_total_tsx_insertion to achieve 90% table utilization, which may exercise more core cases.
next prev parent reply other threads:[~2018-09-29 0:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-27 6:41 Jananee Parthasarathy
2018-09-29 0:12 ` Wang, Yipeng1 [this message]
2018-11-02 12:01 ` [dpdk-dev] [PATCH v2] " Jananee Parthasarathy
2018-11-06 1:45 ` Thomas Monjalon
-- strict thread matches above, loose matches on Subject: below --
2018-09-27 6:38 [dpdk-dev] [PATCH] " Naga Suresh Somarowthu
2018-11-01 17:39 ` Lipiec, Herakliusz
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=D2C4A16CA39F7F4E8E384D204491D7A6614E967B@FMSMSX151.amr.corp.intel.com \
--to=yipeng1.wang@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=jananeex.m.parthasarathy@intel.com \
--cc=naga.sureshx.somarowthu@intel.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=reshma.pattan@intel.com \
--cc=sameh.gobriel@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).