> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Thursday, 26 October 2023 21.51
>
> 26/10/2023 18:50, Morten Brørup:
> > > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > > Sent: Thursday, 26 October 2023 18.07
[...]
> > > For average realtime thread, I suggest the API
> > >
On Thu, 26 Oct 2023 21:55:24 +0200
Thomas Monjalon wrote:
> > To be safe the sleep has to be longer than the system clock tick.
> > Most systems are built today with HZ=250 but really should be using HZ=1000
> > on modern CPU's.
>
> If it has to be more than 1 ms,
> we should mention it is a s
26/10/2023 18:28, Stephen Hemminger:
> On Thu, 26 Oct 2023 16:08:02 +0200
> Morten Brørup wrote:
>
> > > > In our recent tests, nanosleep() itself took around 50 us. So you need
> > > > to
> > > sleep longer than that for your thread not to be runnable when the
> > > nanosleep()
> > > wakes u
26/10/2023 18:50, Morten Brørup:
> > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > Sent: Thursday, 26 October 2023 18.07
> >
> > 26/10/2023 17:54, Bruce Richardson:
> > > On Thu, Oct 26, 2023 at 04:59:51PM +0200, Morten Brørup wrote:
> > > > > From: Morten Brørup [mailto:m...@smartsharesy
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Thursday, 26 October 2023 18.07
>
> 26/10/2023 17:54, Bruce Richardson:
> > On Thu, Oct 26, 2023 at 04:59:51PM +0200, Morten Brørup wrote:
> > > > From: Morten Brørup [mailto:m...@smartsharesystems.com]
> > > > Sent: Thursday, 26 October
On Thu, 26 Oct 2023 16:08:02 +0200
Morten Brørup wrote:
> > > In our recent tests, nanosleep() itself took around 50 us. So you need to
> > >
> > sleep longer than that for your thread not to be runnable when the
> > nanosleep()
> > wakes up again, because 50 us has already passed in "nanosle
26/10/2023 17:54, Bruce Richardson:
> On Thu, Oct 26, 2023 at 04:59:51PM +0200, Morten Brørup wrote:
> > > From: Morten Brørup [mailto:m...@smartsharesystems.com]
> > > Sent: Thursday, 26 October 2023 16.50
> > >
> > > > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > > > Sent: Thursday, 26
On Thu, Oct 26, 2023 at 04:59:51PM +0200, Morten Brørup wrote:
> > From: Morten Brørup [mailto:m...@smartsharesystems.com]
> > Sent: Thursday, 26 October 2023 16.50
> >
> > > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > > Sent: Thursday, 26 October 2023 16.31
> > >
> > > 26/10/2023 16:08
> From: Morten Brørup [mailto:m...@smartsharesystems.com]
> Sent: Thursday, 26 October 2023 16.50
>
> > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > Sent: Thursday, 26 October 2023 16.31
> >
> > 26/10/2023 16:08, Morten Brørup:
> > > > From: Thomas Monjalon [mailto:tho...@monjalon.net]
>
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Thursday, 26 October 2023 16.31
>
> 26/10/2023 16:08, Morten Brørup:
> > > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > > Sent: Thursday, 26 October 2023 16.05
> > >
> > > 26/10/2023 15:57, Morten Brørup:
> > > > > From: Morten
26/10/2023 16:08, Morten Brørup:
> > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > Sent: Thursday, 26 October 2023 16.05
> >
> > 26/10/2023 15:57, Morten Brørup:
> > > > From: Morten Brørup [mailto:m...@smartsharesystems.com]
> > > > Sent: Thursday, 26 October 2023 15.45
> > > >
> > > > >
On Thu, Oct 26, 2023 at 3:57 PM Morten Brørup
wrote:
>
> > From: Morten Brørup [mailto:m...@smartsharesystems.com]
> > Sent: Thursday, 26 October 2023 15.45
> >
> > > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > > Sent: Thursday, 26 October 2023 15.37
> > >
> > > 25/10/2023 18:31, Thoma
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Thursday, 26 October 2023 16.05
>
> 26/10/2023 15:57, Morten Brørup:
> > > From: Morten Brørup [mailto:m...@smartsharesystems.com]
> > > Sent: Thursday, 26 October 2023 15.45
> > >
> > > > From: Thomas Monjalon [mailto:tho...@monjalon.ne
26/10/2023 15:57, Morten Brørup:
> > From: Morten Brørup [mailto:m...@smartsharesystems.com]
> > Sent: Thursday, 26 October 2023 15.45
> >
> > > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > > Sent: Thursday, 26 October 2023 15.37
> > >
> > > 25/10/2023 18:31, Thomas Monjalon:
> > > > Rea
> From: Morten Brørup [mailto:m...@smartsharesystems.com]
> Sent: Thursday, 26 October 2023 15.45
>
> > From: Thomas Monjalon [mailto:tho...@monjalon.net]
> > Sent: Thursday, 26 October 2023 15.37
> >
> > 25/10/2023 18:31, Thomas Monjalon:
> > > Real-time thread priority was been forbidden on Unix
> From: Thomas Monjalon [mailto:tho...@monjalon.net]
> Sent: Thursday, 26 October 2023 15.37
>
> 25/10/2023 18:31, Thomas Monjalon:
> > Real-time thread priority was been forbidden on Unix
> > because of problems they can cause.
> > Warnings and helpers are added to avoid deadlocks,
> > so real-ti
25/10/2023 18:31, Thomas Monjalon:
> Real-time thread priority was been forbidden on Unix
> because of problems they can cause.
> Warnings and helpers are added to avoid deadlocks,
> so real-time can be allowed on all systems.
Unit test is failing:
DPDK:fast-tests / threads_autotest TIMEOUT 6
Real-time thread priority was been forbidden on Unix
because of problems they can cause.
Warnings and helpers are added to avoid deadlocks,
so real-time can be allowed on all systems.
Thomas Monjalon (2):
eal: add thread yield functions
eal/unix: allow creating thread with real-time priority
18 matches
Mail list logo
