From: Feifei Wang <feifei.wang2@arm.com>
Cc: dev@dpdk.org, nd@arm.com, Feifei Wang <feifei.wang2@arm.com>
Subject: [dpdk-dev] [RFC PATCH v1 0/6] refactor smp barriers in app/eventdev
Date: Tue, 22 Dec 2020 11:22:31 +0800 [thread overview]
Message-ID: <20201222032237.36046-1-feifei.wang2@arm.com> (raw)
For smp barriers in app/eventdev, remove the unnecessary barriers or
replace them with thread fence.
Feifei Wang (6):
app/eventdev: fix SMP barrier bugs for perf test
app/eventdev: remove unnecessary barriers for perf test
app/eventdev: replace wmb with thread fence for perf test
app/eventdev: add release barriers for pipeline test
app/eventdev: remove unnecessary barriers for pipeline test
app/eventdev: remove unnecessary barriers for order test
app/test-eventdev/test_order_common.h | 2 -
app/test-eventdev/test_perf_common.c | 4 --
app/test-eventdev/test_perf_common.h | 14 +++++-
app/test-eventdev/test_pipeline_common.c | 1 -
app/test-eventdev/test_pipeline_queue.c | 64 +++++++++++++++++++++---
5 files changed, 68 insertions(+), 17 deletions(-)
--
2.17.1
next reply other threads:[~2020-12-22 3:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 3:22 Feifei Wang [this message]
2020-12-22 3:22 ` [dpdk-dev] [RFC PATCH v1 1/6] app/eventdev: fix SMP barrier bugs for perf test Feifei Wang
2020-12-22 3:22 ` [dpdk-dev] [RFC PATCH v1 2/6] app/eventdev: remove unnecessary barriers " Feifei Wang
2020-12-22 3:22 ` [dpdk-dev] [RFC PATCH v1 3/6] app/eventdev: replace wmb with thread fence " Feifei Wang
2020-12-22 3:22 ` [dpdk-dev] [RFC PATCH v1 4/6] app/eventdev: add release barriers for pipeline test Feifei Wang
2020-12-22 3:22 ` [dpdk-dev] [RFC PATCH v1 5/6] app/eventdev: remove unnecessary " Feifei Wang
2020-12-22 3:22 ` [dpdk-dev] [RFC PATCH v1 6/6] app/eventdev: remove unnecessary barriers for order test Feifei Wang
2020-12-22 5:07 [dpdk-dev] [RFC PATCH v1 0/6] refactor smp barriers in app/eventdev Feifei Wang
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=20201222032237.36046-1-feifei.wang2@arm.com \
--to=feifei.wang2@arm.com \
--cc=dev@dpdk.org \
--cc=nd@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).