From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Yang <phil.yang@arm.com>
Cc: david.marchand@redhat.com, dev@dpdk.org, aconole@redhat.com,
Honnappa.Nagarahalli@arm.com, Ruifeng.Wang@arm.com, nd@arm.com
Subject: Re: [dpdk-dev] [PATCH v2] test/atomic: reduce the number of loops to avoid timeouts
Date: Mon, 12 Jun 2023 20:37:59 -0700 [thread overview]
Message-ID: <20230612203759.71a139ec@hermes.local> (raw)
In-Reply-To: <1595907697-20260-1-git-send-email-phil.yang@arm.com>
On Tue, 28 Jul 2020 11:41:37 +0800
Phil Yang <phil.yang@arm.com> wrote:
> Reduce the number of loops to 10K to avoid the meson test timeout
> warning.
>
> For example:
> $ sudo meson test -C build --suite DPDK:fast-tests / atomic_autotest -t 50
> [...]
> 1/1 DPDK:fast-tests / atomic_autotest OK 187.35s
>
> Signed-off-by: Phil Yang <phil.yang@arm.com>
I don't have Arm server to test on but this looks like a serious issue
with Arm performance. FYI the default 1000000 takes 10 seconds on
slow NUC (AMD x86). Is this a problem with the lack of real compare-exchange
and the default atomic retry model for that?
This patch didn't get applied in 3 years but still worth investigating
if anyone has resources.
next prev parent reply other threads:[~2023-06-13 3:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 4:16 [dpdk-dev] [PATCH 1/2] test/mcslock: move performance test to perf tests Phil Yang
2020-03-23 4:16 ` [dpdk-dev] [PATCH 2/2] test/atomic: reduce the number of loops to avoid timeouts Phil Yang
2020-07-28 3:41 ` [dpdk-dev] [PATCH v2] " Phil Yang
2020-09-17 9:17 ` Juraj Linkeš
2023-06-13 3:37 ` Stephen Hemminger [this message]
2020-07-23 2:36 ` [dpdk-dev] [PATCH 1/2] test/mcslock: move performance test to perf tests Phil Yang
2020-07-23 15:14 ` Aaron Conole
2020-07-28 3:24 ` [dpdk-dev] [PATCH v2] " Phil Yang
2020-09-17 9:16 ` Juraj Linkeš
2023-06-12 21:23 ` [dpdk-dev] [PATCH 1/2] " Stephen Hemminger
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=20230612203759.71a139ec@hermes.local \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=Ruifeng.Wang@arm.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=nd@arm.com \
--cc=phil.yang@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).