> From: Tyler Retzlaff [mailto:roret...@linux.microsoft.com]
> Sent: Thursday, 7 March 2024 19.37
>
> On Thu, Mar 07, 2024 at 07:06:26PM +0100, David Marchand wrote:
> > On Thu, Mar 7, 2024 at 3:16 PM David Marchand
> wrote:
> > >
> > > Busy looping on RTE_MAX_LCORES threads is too heavy in some
On Thu, Mar 07, 2024 at 07:06:26PM +0100, David Marchand wrote:
> On Thu, Mar 7, 2024 at 3:16 PM David Marchand
> 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 synchronisa
On Thu, Mar 7, 2024 at 3:16 PM David Marchand 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
> Acked-by: Luca Boccassi
I
On Thu, 7 Mar 2024 15:16:06 +0100
David Marchand wrote:
> +#ifndef _POSIX_PRIORITY_SCHEDULING
> +/* sched_yield(2):
> + * POSIX systems on which sched_yield() is available define _POSIX_PRIOR‐
> + * ITY_SCHEDULING in .
> + */
> +#define sched_yield()
> +#endif
Could you fix the awkward line br
On Thu, 7 Mar 2024 15:16:06 +0100
David Marchand 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
> Acked-by: Luca Boccassi
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
Acked-by: Luca Boccassi
---
Changes since v1:
- fix build with mingw,
---
app/test/test_lco
6 matches
Mail list logo