> > > However, if a timer expires quickly enough, there exists the
> > > following race condition that causes the timer_manage() routine to
> > > misinterpret a timer in CONFIG state, resulting in lost timers:
> > >
> > > - Thread A:
> > > - starts a timer with rte_timer_reset()
> > > - the tim
; Subject: Re: [dpdk-dev] [PATCH 1/1] timer: fix race condition
>
> Who could review this fix please?
>
> 29/11/2018 19:53, Erik Gabriel Carrillo:
> > rte_timer_manage() adds expired timers to a "run list", and walks the
> > list, transitioning each timer from the PE
Who could review this fix please?
29/11/2018 19:53, Erik Gabriel Carrillo:
> rte_timer_manage() adds expired timers to a "run list", and walks the
> list, transitioning each timer from the PENDING to the RUNNING state.
> If another lcore resets or stops the timer at precisely this
> moment, the ti
rte_timer_manage() adds expired timers to a "run list", and walks the
list, transitioning each timer from the PENDING to the RUNNING state.
If another lcore resets or stops the timer at precisely this
moment, the timer state would instead be set to CONFIG by that other
lcore, which would cause time
4 matches
Mail list logo
