From: Thomas Monjalon <thomas@monjalon.net>
To: Dharmik Thakkar <dharmik.thakkar@arm.com>
Cc: dev@dpdk.org, Yipeng Wang <yipeng1.wang@intel.com>,
Sameh Gobriel <sameh.gobriel@intel.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Pablo de Lara <pablo.de.lara.guarch@intel.com>,
honnappa.nagarahalli@arm.com
Subject: Re: [PATCH v4 2/2] test/hash: lock-free rw concurrency test ext bkt
Date: Tue, 02 Apr 2019 02:57:37 +0200 [thread overview]
Message-ID: <2434371.7uYfYzBtHE@xps> (raw)
In-Reply-To: <20190401230830.17931-3-dharmik.thakkar@arm.com>
02/04/2019 01:08, Dharmik Thakkar:
> Add unit test to check for hash lookup and bulk-lookup perf for
> extendable bucket feature.
> It is tested with both lock-free enabled and lock-free disabled case.
>
> Test includes:
>
> - hash lookup on keys in ext bkt
> - hash delete causing key-shifts of keys from ext bkt to secondary bkt
>
> Suggested-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Signed-off-by: Dharmik Thakkar <dharmik.thakkar@arm.com>
> Acked-by: Yipeng Wang <yipeng1.wang@intel.com>
> ---
> v4:
> - Add Acked-by tag.
FYI, no need to send a new version just for this.
Please run devtools/test-meson-builds.sh.
When building build-clang-static, I see this error:
app/test/test_hash_readwrite_lf.c:670:13: error:
variable 'key_cnt' is used uninitialized whenever 'if' condition is false
next prev parent reply other threads:[~2019-04-02 0:57 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 22:35 [PATCH 0/2] hash: add lock free support for ext bkt Dharmik Thakkar
2019-03-20 22:35 ` [PATCH 1/2] hash: add lock free support for extendable bucket Dharmik Thakkar
2019-03-22 23:48 ` Wang, Yipeng1
2019-03-25 20:10 ` Dharmik Thakkar
2019-03-20 22:35 ` [PATCH 2/2] test/hash: lock-free rw concurrency test ext bkt Dharmik Thakkar
2019-03-25 21:08 ` [PATCH v2 0/2] hash: add lock free support for " Dharmik Thakkar
2019-03-25 21:08 ` [PATCH v2 1/2] hash: add lock free support for extendable bucket Dharmik Thakkar
2019-04-01 18:20 ` Wang, Yipeng1
2019-04-01 20:16 ` Dharmik Thakkar
2019-03-25 21:08 ` [PATCH v2 2/2] test/hash: lock-free rw concurrency test ext bkt Dharmik Thakkar
2019-04-01 18:55 ` Wang, Yipeng1
2019-04-01 20:06 ` Dharmik Thakkar
2019-04-01 22:18 ` [PATCH v3 0/2] hash: add lock free support for " Dharmik Thakkar
2019-04-01 22:18 ` [PATCH v3 1/2] hash: add lock free support for extendable bucket Dharmik Thakkar
2019-04-01 22:18 ` [PATCH v3 2/2] test/hash: lock-free rw concurrency test ext bkt Dharmik Thakkar
2019-04-01 22:52 ` Wang, Yipeng1
2019-04-01 23:08 ` [PATCH v4 0/2] hash: add lock free support for " Dharmik Thakkar
2019-04-01 23:08 ` [PATCH v4 1/2] hash: add lock free support for extendable bucket Dharmik Thakkar
2019-04-01 23:08 ` [PATCH v4 2/2] test/hash: lock-free rw concurrency test ext bkt Dharmik Thakkar
2019-04-02 0:57 ` Thomas Monjalon [this message]
2019-04-02 19:44 ` Dharmik Thakkar
2019-04-02 19:44 ` [PATCH v5 0/2] hash: add lock free support for " Dharmik Thakkar
2019-04-02 19:44 ` [PATCH v5 1/2] hash: add lock free support for extendable bucket Dharmik Thakkar
2019-04-02 19:44 ` [PATCH v5 2/2] test/hash: lock-free rw concurrency test ext bkt Dharmik Thakkar
2019-04-03 18:56 ` [PATCH v5 0/2] hash: add lock free support for " 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=2434371.7uYfYzBtHE@xps \
--to=thomas@monjalon.net \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dharmik.thakkar@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=pablo.de.lara.guarch@intel.com \
--cc=sameh.gobriel@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.