From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Dharmik Thakkar <dharmik.thakkar@arm.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>
Cc: dev@dpdk.org, stable@dpdk.org, Yipeng Wang <yipeng1.wang@intel.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] test/hash: reset iter and found in perf test
Date: Fri, 11 Jan 2019 17:10:09 +0000 [thread overview]
Message-ID: <2d2fbf94-02a4-0215-1fd6-65bd9f32305a@intel.com> (raw)
In-Reply-To: <20181129183855.9361-1-dharmik.thakkar@arm.com>
On 11/29/2018 6:38 PM, Dharmik Thakkar wrote:
> Reset 'iter' and 'tbl_rw_test_param.found' on each iteration
> to give correct result for lost and duplicated keys.
>
> Fixes: 0eb3726ebcf14 ("test/hash: add test for read/write concurrency")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dharmik Thakkar <dharmik.thakkar@arm.com>
> ---
> test/test/test_hash_readwrite.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/test/test/test_hash_readwrite.c b/test/test/test_hash_readwrite.c
> index 6b695ce6e444..be93a2ebd270 100644
> --- a/test/test/test_hash_readwrite.c
> +++ b/test/test/test_hash_readwrite.c
> @@ -361,7 +361,6 @@ test_hash_readwrite_perf(struct perf *perf_results, int use_htm,
>
> const void *next_key;
> void *next_data;
> - uint32_t iter = 0;
> int use_jhash = 0;
>
> uint32_t duplicated_keys = 0;
> @@ -536,6 +535,8 @@ test_hash_readwrite_perf(struct perf *perf_results, int use_htm,
>
> rte_eal_mp_wait_lcore();
>
> + uint32_t iter = 0;
Logically looks good. Only we don't tend to declare the variables in the middle
of the scope, you may prefer to keep deceleration at its place but set 'iter' to
zero here.
> + memset(tbl_rw_test_param.found, 0, TOTAL_ENTRY);
> while (rte_hash_iterate(tbl_rw_test_param.h,
> &next_key, &next_data, &iter) >= 0) {
> /* Search for the key in the list of keys added .*/
> @@ -619,7 +620,7 @@ test_hash_readwrite_main(void)
> if (rte_lcore_count() <= 2) {
> printf("More than two lcores are required "
> "to do read write test\n");
> - return 0;
> + return -1;
This is something not mentioned in the commit log, changes the default return
value of test when not enough resources provided, cc'ed Yipeng for comment.
If decided to keep this change, please update commit log to mention from it.
next prev parent reply other threads:[~2019-01-11 17:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 18:38 [dpdk-dev] " Dharmik Thakkar
2019-01-11 17:10 ` Ferruh Yigit [this message]
2019-01-11 18:37 ` [dpdk-dev] [dpdk-stable] " Wang, Yipeng1
2019-01-14 7:12 ` Dharmik Thakkar
2019-01-14 9:23 ` [dpdk-dev] [PATCH v2] " Dharmik Thakkar
2019-01-14 23:19 ` 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=2d2fbf94-02a4-0215-1fd6-65bd9f32305a@intel.com \
--to=ferruh.yigit@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dharmik.thakkar@arm.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=stable@dpdk.org \
--cc=yipeng1.wang@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).