From: Konstantin Ananyev <konstantin.ananyev@intel.com>
To: dev@dpdk.org
Cc: honnappa.nagarahalli@arm.com, feifei.wang2@arm.com,
Konstantin Ananyev <konstantin.ananyev@intel.com>
Subject: [dpdk-dev] [PATCH v2 0/2] extend test coverage for ring PEEK API
Date: Thu, 2 Jul 2020 15:10:25 +0100 [thread overview]
Message-ID: <20200702141027.18447-1-konstantin.ananyev@intel.com> (raw)
In-Reply-To: <20200630162139.19512-1-konstantin.ananyev@intel.com>
Introduce new test case to test ST peek API.
Changes name for MT peek ring test to follow same naming convention.
Konstantin Ananyev (2):
test/ring: add stress test for ST peek API
test/ring: rearrange names for ring stress tests
app/test/Makefile | 3 +-
app/test/meson.build | 3 +-
...ek_stress.c => test_ring_mt_peek_stress.c} | 2 +-
app/test/test_ring_st_peek_stress.c | 54 +++++++++++++++++++
app/test/test_ring_stress.c | 7 ++-
app/test/test_ring_stress.h | 3 +-
6 files changed, 66 insertions(+), 6 deletions(-)
rename app/test/{test_ring_peek_stress.c => test_ring_mt_peek_stress.c} (94%)
create mode 100644 app/test/test_ring_st_peek_stress.c
--
2.17.1
next prev parent reply other threads:[~2020-07-02 14:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 16:21 [dpdk-dev] [PATCH] test/ring: add stress test for ST peek API Konstantin Ananyev
2020-06-30 23:01 ` Honnappa Nagarahalli
2020-07-01 10:34 ` Ananyev, Konstantin
2020-07-01 14:05 ` Honnappa Nagarahalli
2020-07-02 14:10 ` Konstantin Ananyev [this message]
2020-07-02 14:10 ` [dpdk-dev] [PATCH v2 1/2] " Konstantin Ananyev
2020-07-02 16:18 ` Honnappa Nagarahalli
2020-07-02 14:10 ` [dpdk-dev] [PATCH v2 2/2] test/ring: rearrange names for ring stress tests Konstantin Ananyev
2020-07-02 16:18 ` Honnappa Nagarahalli
2020-07-03 1:46 ` [dpdk-dev] 回复: " Feifei Wang
2020-07-03 2:37 ` [dpdk-dev] " Honnappa Nagarahalli
2020-07-03 3:01 ` [dpdk-dev] 回复: " Feifei Wang
2020-07-03 10:40 ` [dpdk-dev] [PATCH v2 0/2] extend test coverage for ring PEEK API 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=20200702141027.18447-1-konstantin.ananyev@intel.com \
--to=konstantin.ananyev@intel.com \
--cc=dev@dpdk.org \
--cc=feifei.wang2@arm.com \
--cc=honnappa.nagarahalli@arm.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).