From: Stephen Hemminger <stephen@networkplumber.org>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, bluca@debian.org
Subject: Re: [PATCH] test/lcores: reduce cpu consumption
Date: Thu, 7 Mar 2024 08:54:25 -0800 [thread overview]
Message-ID: <20240307085425.1feda85c@hermes.local> (raw)
In-Reply-To: <20240307113324.845309-1-david.marchand@redhat.com>
On Thu, 7 Mar 2024 12:33:24 +0100
David Marchand <david.marchand@redhat.com> wrote:
> Busy looping on RTE_MAX_LCORES threads is too heavy in some CI
> environments running the fast-test testsuite.
> Ask for a reschedule at the threads synchronisation points.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
You could use rte_pause here but full yield is better for test cases.
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
prev parent reply other threads:[~2024-03-07 16:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 11:33 David Marchand
2024-03-07 12:09 ` Luca Boccassi
2024-03-07 14:16 ` [PATCH v2] " David Marchand
2024-03-07 17:06 ` Stephen Hemminger
2024-03-07 17:08 ` Stephen Hemminger
2024-03-07 18:06 ` David Marchand
2024-03-07 18:36 ` Tyler Retzlaff
2024-03-07 19:25 ` Morten Brørup
2024-03-07 16:54 ` 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=20240307085425.1feda85c@hermes.local \
--to=stephen@networkplumber.org \
--cc=bluca@debian.org \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).