From: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
To: agupta3@marvell.com, yipeng1.wang@intel.com,
sameh.gobriel@intel.com, honnappa.nagarahalli@arm.com
Cc: thomas@monjalon.net, david.marchand@redhat.com, dev@dpdk.org, nd@arm.com
Subject: [dpdk-dev] [PATCH v2 0/5] test/meson: fix hash readwrite timeout failure
Date: Mon, 3 Feb 2020 13:49:07 -0600 [thread overview]
Message-ID: <20200203194912.4669-1-honnappa.nagarahalli@arm.com> (raw)
In-Reply-To: <1567748973-24192-1-git-send-email-agupta3@marvell.com>
V2 changes:
- Remove duplicated code in the existing patch
- Add lock-free option to hash read-write functional test cases
- Move existing loack-free test cases to performance tests
- A typo fix in the comments for lock-free extendable table feature
V1 changes:
- hash_readwrite and hash_readwrite lockfree meson test was
taking longer time to complete. The test always get TIMEOUT.
- hash readwrtie test is split into functional and perf tests
and moved to dpdk fast and perf testsuite accordingly.
- hash readwrite lockfree is moved to dpdk perf testsuite.
Amit Gupta (1):
test/meson: hash test split into shorter subtests
Honnappa Nagarahalli (4):
test/hash: remove duplicated test code
test/hash: add lock free reader writer functional tests
test/hash: move reader writer lock free tests to perf tests
hash: correct lock free extendable table support
app/test/Makefile | 2 +-
app/test/autotest_data.py | 14 ++-
app/test/meson.build | 7 +-
app/test/test_hash_readwrite.c | 117 +++++++++++++-----
...ite_lf.c => test_hash_readwrite_lf_perf.c} | 7 +-
lib/librte_hash/rte_hash.h | 2 -
6 files changed, 107 insertions(+), 42 deletions(-)
rename app/test/{test_hash_readwrite_lf.c => test_hash_readwrite_lf_perf.c} (99%)
--
2.17.1
next prev parent reply other threads:[~2020-02-03 19:49 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 5:49 [dpdk-dev] [PATCH 0/2] " agupta3
2019-09-06 5:49 ` [dpdk-dev] [PATCH 1/2] test/meson: hash test split into shorter subtests agupta3
2019-09-11 17:05 ` Wang, Yipeng1
2019-10-17 5:02 ` Amit Gupta
2019-11-01 4:54 ` Amit Gupta
2019-11-01 17:04 ` Wang, Yipeng1
2019-11-05 16:37 ` Ferruh Yigit
2019-11-07 3:32 ` [dpdk-dev] [EXT] " Amit Gupta
2019-12-31 4:56 ` Amit Gupta
2019-09-06 5:49 ` [dpdk-dev] [PATCH 2/2] test/meson: hash lf test moved to dpdk perf testsuite agupta3
2019-09-11 17:13 ` Wang, Yipeng1
2019-09-12 15:00 ` Honnappa Nagarahalli
2019-09-13 8:24 ` Amit Gupta
2019-09-13 8:12 ` [dpdk-dev] [PATCH v2 1/1] " agupta3
2019-09-13 14:40 ` Aaron Conole
2019-09-13 15:09 ` Wang, Yipeng1
2019-09-13 15:46 ` Honnappa Nagarahalli
2019-09-16 4:39 ` Amit Gupta
2019-10-17 4:57 ` Amit Gupta
2019-10-17 13:16 ` Aaron Conole
2019-10-24 7:22 ` David Marchand
2019-09-13 8:15 ` agupta3
2019-09-11 5:55 ` [dpdk-dev] [PATCH 0/2] test/meson: fix hash readwrite timeout failure Amit Gupta
2020-02-03 19:49 ` Honnappa Nagarahalli [this message]
2020-02-03 19:49 ` [dpdk-dev] [PATCH v2 1/5] test/meson: hash test split into shorter subtests Honnappa Nagarahalli
2020-02-03 19:49 ` [dpdk-dev] [PATCH v2 2/5] test/hash: remove duplicated test code Honnappa Nagarahalli
2020-02-05 8:48 ` David Marchand
2020-02-05 16:42 ` David Marchand
2020-02-03 19:49 ` [dpdk-dev] [PATCH v2 3/5] test/hash: add lock free reader writer functional tests Honnappa Nagarahalli
2020-02-05 9:07 ` David Marchand
2020-02-05 16:22 ` Honnappa Nagarahalli
2020-02-05 16:41 ` David Marchand
2020-02-05 19:34 ` Wang, Yipeng1
2020-02-05 19:52 ` Honnappa Nagarahalli
2020-02-05 19:57 ` Wang, Yipeng1
2020-02-03 19:49 ` [dpdk-dev] [PATCH v2 4/5] test/hash: move reader writer lock free tests to perf tests Honnappa Nagarahalli
2020-02-03 19:49 ` [dpdk-dev] [PATCH v2 5/5] hash: correct lock free extendable table support Honnappa Nagarahalli
2020-02-05 18:41 ` [dpdk-dev] [PATCH v2 0/5] test/meson: fix hash readwrite timeout failure David Marchand
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=20200203194912.4669-1-honnappa.nagarahalli@arm.com \
--to=honnappa.nagarahalli@arm.com \
--cc=agupta3@marvell.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=sameh.gobriel@intel.com \
--cc=thomas@monjalon.net \
--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).