From: Feifei Wang <feifei.wang2@arm.com>
Cc: dev@dpdk.org, nd@arm.com, Honnappa.Nagarahalli@arm.com,
ruifeng.wang@arm.com, Feifei Wang <feifei.wang2@arm.com>
Subject: [dpdk-dev] [PATCH v1 0/2] remove smp barriers in app/test
Date: Tue, 22 Dec 2020 14:30:52 +0800 [thread overview]
Message-ID: <20201222063054.44429-1-feifei.wang2@arm.com> (raw)
For smp barriers in app/test, remove the unnecessary barriers and fix
some bugs.
Feifei Wang (2):
app/test: remove unnecessary barriers for ring stress test
app/test: collect perf data after worker threads exit
app/test/test_ring_stress_impl.h | 5 +----
app/test/test_trace_perf.c | 5 ++---
2 files changed, 3 insertions(+), 7 deletions(-)
--
2.17.1
next reply other threads:[~2020-12-22 6:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 6:30 Feifei Wang [this message]
2020-12-22 6:30 ` [dpdk-dev] [PATCH v1 1/2] app/test: remove unnecessary barriers for ring stress test Feifei Wang
2020-12-22 12:42 ` Ananyev, Konstantin
2021-01-27 23:00 ` Honnappa Nagarahalli
2021-01-28 14:43 ` Ananyev, Konstantin
2021-01-29 3:17 ` Honnappa Nagarahalli
2021-01-29 4:58 ` Stephen Hemminger
2021-01-30 1:24 ` Honnappa Nagarahalli
2021-02-01 8:37 ` [dpdk-dev] 回复: " Feifei Wang
2021-02-01 13:50 ` [dpdk-dev] " Ananyev, Konstantin
2021-02-03 16:24 ` Honnappa Nagarahalli
2021-02-01 8:48 ` [dpdk-dev] 回复: " Feifei Wang
2021-02-01 9:07 ` Feifei Wang
2020-12-22 6:30 ` [dpdk-dev] [PATCH v1 2/2] app/test: collect perf data after worker threads exit Feifei Wang
2021-03-10 2:12 ` [dpdk-dev] [PATCH v3 0/1] remove smp barriers in app/test Feifei Wang
2021-03-10 2:12 ` [dpdk-dev] [PATCH v3 1/1] test/trace: collect perf data after worker threads exit Feifei Wang
2021-03-10 2:15 ` [dpdk-dev] [PATCH v3 0/1] remove smp barriers in app/test Feifei Wang
2021-03-10 2:15 ` [dpdk-dev] [PATCH v3 1/1] test/trace: collect perf data after worker threads exit Feifei Wang
2021-04-14 14:14 ` 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=20201222063054.44429-1-feifei.wang2@arm.com \
--to=feifei.wang2@arm.com \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=ruifeng.wang@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).