From: Stanislaw Kardach <kda@semihalf.com>
To: dev@dpdk.org, david.hunt@intel.com
Cc: upstream@semihalf.com, l.wojciechow@partner.samsung.com,
Stanislaw Kardach <kda@semihalf.com>
Subject: [dpdk-dev] [PATCH v2 0/2] test/distributor: perf burst mode quit fixes
Date: Wed, 28 Apr 2021 16:25:51 +0200 [thread overview]
Message-ID: <20210428142553.1593546-1-kda@semihalf.com> (raw)
In-Reply-To: <20210426163310.1043438-1-kda@semihalf.com>
This series addresses two issues:
1. Worker threads hang when finishing the burst-mode distributor perf
test. This was observed on a RISC-V platform as well as reproduced on
x86.
2. Potential lack of fairness in final wakeup notification distribution
in burst mode. Though this issue was not observed, the change is in
line with the functional tests.
---
RFC -> V2
- Split 2 fixes into separate patches.
- Added review/test/ack tags from the RFC discussion.
---
Stanislaw Kardach (2):
test/distributor: fix worker notification in burst
test/distributor: fix burst flush on worker quit
app/test/test_distributor_perf.c | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
--
2.27.0
next prev parent reply other threads:[~2021-04-28 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210426163404eucas1p13be6ae1bbcc4b947599cb606befd5370@eucas1p1.samsung.com>
2021-04-26 16:33 ` [dpdk-dev] [RFC PATCH] test/distributor: fix burst flush on worker quit Stanislaw Kardach
2021-04-28 7:46 ` Lukasz Wojciechowski
2021-04-28 12:50 ` David Hunt
2021-04-28 12:53 ` Stanisław Kardach
2021-04-28 13:03 ` David Hunt
2021-04-28 13:11 ` David Marchand
2021-04-28 13:22 ` Stanisław Kardach
2021-04-28 14:25 ` Stanislaw Kardach [this message]
2021-04-28 14:25 ` [dpdk-dev] [PATCH v2 1/2] test/distributor: fix worker notification in burst Stanislaw Kardach
2021-04-28 14:25 ` [dpdk-dev] [PATCH v2 2/2] test/distributor: fix burst flush on worker quit Stanislaw Kardach
2021-05-05 14:54 ` [dpdk-dev] [PATCH v2 0/2] test/distributor: perf burst mode quit fixes 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=20210428142553.1593546-1-kda@semihalf.com \
--to=kda@semihalf.com \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=l.wojciechow@partner.samsung.com \
--cc=upstream@semihalf.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).