The resolution of schedule time can be more than 1ns. As result
can happen that 1ns corresponds 0 ticks of timer counter, but if
passed 1ns it's obvious that user wanted to schedule at least once.
Currently it can lead to wait forever, as 0 corresponds to
ODP_SCHED_WAIT, it can block program flow
: [lng-odp] [Patch 1/2] linux-generic: odp_schedule: fix
odp_schdule_wait_time
On 10.09.15 15:16, Savolainen, Petri (Nokia - FI/Espoo) wrote:
Change is OK. The calculation can be changed to use cpu cycle API
(with max CPU hz) later. Time measurement does not have to be accurate,
so we can
Petri,
Are you OK with this change?
On 10.09.15 12:48, Ivan Khoronzhuk wrote:
The resolution of schedule time can be more than 1ns. As result
can happen that 1ns corresponds 0 ticks of timer counter, but if
passed 1ns it's obvious that user wanted to schedule at least once.
Currently it can
o...@kalray.eu
> Cc: Ivan Khoronzhuk
> Subject: [lng-odp] [Patch 1/2] linux-generic: odp_schedule: fix
> odp_schdule_wait_time
>
> The resolution of schedule time can be more than 1ns. As result
> can happen that 1ns corresponds 0 ticks of timer counter, but if
> passed
o: lng-odp@lists.linaro.org; Savolainen, Petri (Nokia - FI/Espoo);
nmo...@kalray.eu
Cc: Ivan Khoronzhuk
Subject: [lng-odp] [Patch 1/2] linux-generic: odp_schedule: fix
odp_schdule_wait_time
The resolution of schedule time can be more than 1ns. As result
can happen that 1ns corresponds 0 ticks of tim
gt; >> -Original Message-
> >> From: EXT Ivan Khoronzhuk [mailto:ivan.khoronz...@linaro.org]
> >> Sent: Thursday, September 10, 2015 12:49 PM
> >> To: lng-odp@lists.linaro.org; Savolainen, Petri (Nokia - FI/Espoo);
> >> nmo...@kalray.eu
> &g
