DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, bluca@debian.org,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH v2] test/lcores: reduce cpu consumption
Date: Thu, 7 Mar 2024 10:36:49 -0800	[thread overview]
Message-ID: <20240307183649.GA22674@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <CAJFAV8xxnqEGFrksqsd-_vUtmHMm_-b-+Q_J6h=D06QS-4NFyg@mail.gmail.com>

On Thu, Mar 07, 2024 at 07:06:26PM +0100, David Marchand wrote:
> On Thu, Mar 7, 2024 at 3:16 PM David Marchand <david.marchand@redhat.com> wrote:
> >
> > Busy looping on RTE_MAX_LCORES threads is too heavy in some CI or build
> > systems running the fast-test testsuite.
> > Ask for a reschedule at the threads synchronisation points.
> >
> > Signed-off-by: David Marchand <david.marchand@redhat.com>
> > Acked-by: Luca Boccassi <bluca@debian.org>
> 
> Ideally, this test should be rewritten with some kind of OS-agnostic
> synchronisation/scheduling API (mutex?).
> But I think it will be enough for now.

It's okay, I'll eventually get to this :)

> 
> I updated the code comment as requested by Stephen.
> 
> Applied, thanks.
> 
> -- 
> David Marchand

  reply	other threads:[~2024-03-07 18:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-07 11:33 [PATCH] " 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 [this message]
2024-03-07 19:25       ` Morten Brørup
2024-03-07 16:54 ` [PATCH] " 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=20240307183649.GA22674@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
    --to=roretzla@linux.microsoft.com \
    --cc=bluca@debian.org \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.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).