On Thu, Aug 21, 2014 at 01:33:49PM +, "Aviv Heller (avheller)"
wrote:
> I have encountered a problem, on version 4.11 of the library, where a timer
> started expired prior to its intended expiry time.
The documentation is far ahead of you here: see "The special problem of
time updates" in t
> In cases where the system is under heavy load (a prevalent case in embedded
> systems), this problem can manifest even if the iteration processing time
> prior to setting the timer is in theory short.
This observation is an indication of a potential issue that an
application is not always quickl
I'm no expert on libev, but sounds like this could be caused due to a
spurious wake up...
On Thu, Aug 21, 2014 at 9:33 AM, Aviv Heller (avheller)
wrote:
> Hi,
>
> I have encountered a problem, on version 4.11 of the library, where a
> timer started expired prior to its intended expiry time.
>
Hi,
I have encountered a problem, on version 4.11 of the library, where a timer
started expired prior to its intended expiry time.
This happened because time_update() is not called by ev_timer_start() prior to
calculating the expiry timestamp, which in cases where a timer is started after
a lo
