From: Stephen Hemminger <stephen@networkplumber.org>
To: Phil Yang <phil.yang@arm.com>
Cc: aconole@redhat.com, maicolgabriel@hotmail.com, dev@dpdk.org,
david.marchand@redhat.com, drc@linux.vnet.ibm.com,
gavin.hu@arm.com, Honnappa.Nagarahalli@arm.com,
ruifeng.wang@arm.com, nd@arm.com
Subject: Re: [dpdk-dev] [PATCH 1/2] test/mcslock: move performance test to perf tests
Date: Mon, 12 Jun 2023 14:23:32 -0700 [thread overview]
Message-ID: <20230612142332.3b2ce587@hermes.local> (raw)
In-Reply-To: <1584936978-11899-1-git-send-email-phil.yang@arm.com>
On Mon, 23 Mar 2020 12:16:17 +0800
Phil Yang <phil.yang@arm.com> wrote:
> The MCS lock performance test takes more than 10 seconds and leads
> to meson test timeout on some platforms. Move the performance test
> into perf tests.
>
> Signed-off-by: Phil Yang <phil.yang@arm.com>
> Reviewed-by: Gavin Hu <gavin.hu@arm.com>
> ---
No, fix the test.
There is no reason that mcslock should be in perf section
but not all the other lock types.
prev parent reply other threads:[~2023-06-12 21:23 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
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 ` Stephen Hemminger [this message]
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=20230612142332.3b2ce587@hermes.local \
--to=stephen@networkplumber.org \
--cc=Honnappa.Nagarahalli@arm.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
--cc=gavin.hu@arm.com \
--cc=maicolgabriel@hotmail.com \
--cc=nd@arm.com \
--cc=phil.yang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.