25/10/2023 17:18, Thomas Monjalon: > 25/10/2023 17:14, Bruce Richardson: > > On Wed, Oct 25, 2023 at 08:08:52AM -0700, Stephen Hemminger wrote: > > > On Wed, 25 Oct 2023 15:44:25 +0200 > > > Thomas Monjalon <tho...@monjalon.net> wrote: > > > > > > > > > > > > > > > I'll try to pass the test by adding a sleep in the test thread. > > > > > > > > > > > > > > > > "sched_yield()" rather than sleep perhaps? Might better convey the > > > > > intention of the call. > > > > > > > > Do we have sched_yield on Windows? > > > > > > Windows has an equivalent but sched_yield() won't work here. > > > Since the DPDK thread is still higher priority than the kernel thread, > > > the scheduler will reschedule the DPDK thread. You need to sleep > > > to let kthread run. > > > > Interesting. Thanks for clarifying the situation. > > Indeed interesting. > I've just sent a v2 before reading this. > > So I should try a v3 with a sleep. > But then I need to find a better name than rte_thread_yield. > Ideas?
I will go with rte_thread_yield_realtime(). Any sleep will suffice on Linux? What about a nanosleep? I suppose Sleep(0) is OK on Windows?
