From: Bruce Richardson <bruce.richardson@intel.com>
To: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Cc: pablo.de.lara.guarch@intel.com, dev@dpdk.org,
yipeng1.wang@intel.com, gavin.hu@arm.com,
dharmik.thakkar@arm.com, nd@arm.com
Subject: Re: [dpdk-dev] [PATCH v5 5/5] test/hash: read-write lock-free concurrency test
Date: Tue, 23 Oct 2018 12:56:37 +0100 [thread overview]
Message-ID: <20181023115637.GF18800@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <1540268524-126673-6-git-send-email-honnappa.nagarahalli@arm.com>
On Mon, Oct 22, 2018 at 11:22:04PM -0500, Honnappa Nagarahalli wrote:
> From: Dharmik Thakkar <dharmik.thakkar@arm.com>
>
> Unit tests to check for hash lookup and bulk-lookup perf
> with lock-free enabled and with lock-free disabled.
> Unit tests performed with readers running in parallel with writers.
>
> Tests include:
>
> - hash lookup on existing keys with:
> - hash add causing NO key-shifts of existing keys in the table
>
> - hash lookup on existing keys likely to be on shift-path with:
> - hash add causing key-shifts of existing keys in the table
>
> - hash lookup on existing keys NOT likely to be on shift-path with:
> - hash add causing key-shifts of existing keys in the table
>
> - hash lookup on non-existing keys with:
> - hash add causing NO key-shifts of existing keys in the table
> - hash add causing key-shifts of existing keys in the table
>
> - hash lookup on keys likely to be on shift-path with:
> - multiple writers causing key-shifts of existing keys in the table
>
> Signed-off-by: Dharmik Thakkar <dharmik.thakkar@arm.com>
> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> Reviewed-by: Yipeng Wang <yipeng1.wang@intel.com>
> ---
> test/test/Makefile | 1 +
> test/test/meson.build | 1 +
> test/test/test_hash_readwrite_lf.c | 1220 ++++++++++++++++++++++++++++++++++++
> 3 files changed, 1222 insertions(+)
> create mode 100644 test/test/test_hash_readwrite_lf.c
>
> diff --git a/test/test/Makefile b/test/test/Makefile
> index 8c347e4..1b5c070 100644
> --- a/test/test/Makefile
> +++ b/test/test/Makefile
> @@ -116,6 +116,7 @@ SRCS-$(CONFIG_RTE_LIBRTE_HASH) += test_hash_functions.c
> SRCS-$(CONFIG_RTE_LIBRTE_HASH) += test_hash_scaling.c
> SRCS-$(CONFIG_RTE_LIBRTE_HASH) += test_hash_multiwriter.c
> SRCS-$(CONFIG_RTE_LIBRTE_HASH) += test_hash_readwrite.c
> +SRCS-$(CONFIG_RTE_LIBRTE_HASH) += test_hash_readwrite_lf.c
>
> SRCS-$(CONFIG_RTE_LIBRTE_LPM) += test_lpm.c
> SRCS-$(CONFIG_RTE_LIBRTE_LPM) += test_lpm_perf.c
> diff --git a/test/test/meson.build b/test/test/meson.build
> index 90d6607..d352b94 100644
> --- a/test/test/meson.build
> +++ b/test/test/meson.build
> @@ -46,6 +46,7 @@ test_sources = files('commands.c',
> 'test_hash_multiwriter.c',
> 'test_hash_readwrite.c',
> 'test_hash_perf.c',
> + 'test_hash_readwrite_lf.c',
> 'test_hash_scaling.c',
> 'test_interrupts.c',
> 'test_kni.c',
Two minor issues I spot, both related:
* You also need to add the test to the list of test names, so that it can be
called using "meson test".
* For running the autotests built using make, a new entry should be added to
autotest_data.py to run this new test case.
/Bruce
prev parent reply other threads:[~2018-10-23 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 4:21 [dpdk-dev] [PATCH v5 0/5] Address reader-writer concurrency in rte_hash Honnappa Nagarahalli
2018-10-23 4:22 ` [dpdk-dev] [PATCH v5 1/5] hash: separate multi-writer from rw-concurrency Honnappa Nagarahalli
2018-10-23 10:25 ` Bruce Richardson
2018-10-23 4:22 ` [dpdk-dev] [PATCH v5 2/5] hash: support do not free on delete Honnappa Nagarahalli
2018-10-23 10:30 ` Bruce Richardson
2018-10-23 4:22 ` [dpdk-dev] [PATCH v5 3/5] hash: fix key store element alignment Honnappa Nagarahalli
2018-10-23 10:31 ` Bruce Richardson
2018-10-23 4:22 ` [dpdk-dev] [PATCH v5 4/5] hash: add lock-free read-write concurrency Honnappa Nagarahalli
2018-10-23 11:52 ` Bruce Richardson
2018-10-23 4:22 ` [dpdk-dev] [PATCH v5 5/5] test/hash: read-write lock-free concurrency test Honnappa Nagarahalli
2018-10-23 11:54 ` Bruce Richardson
2018-10-23 14:15 ` Honnappa Nagarahalli
2018-10-23 14:20 ` Bruce Richardson
2018-10-23 15:52 ` Honnappa Nagarahalli
2018-10-23 11:56 ` Bruce Richardson [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=20181023115637.GF18800@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=dharmik.thakkar@arm.com \
--cc=gavin.hu@arm.com \
--cc=honnappa.nagarahalli@arm.com \
--cc=nd@arm.com \
--cc=pablo.de.lara.guarch@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 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).