[dpdk-dev] [RFC v2] eal: simplify the implementation of rte_ctrl_thread_create
Stephen Hemminger
stephen at networkplumber.org
Tue Aug 24 23:30:58 CEST 2021
On Tue, 24 Aug 2021 20:03:03 +0000
Honnappa Nagarahalli <Honnappa.Nagarahalli at arm.com> wrote:
> > One difference between this implementation and the previous one is this busy
> > loop. rte_pause() relaxes the cpu, but will not make the calling thread to sleep
> > and wait for the sync event. So here we can spin a quite long time until the
> > other thread is scheduled by the OS.
> Yes, this is a difference. We could add a microsleep to allow for the OS to un-schedule the current thread.
Why not use sched_yield() here?
More information about the dev
mailing list