93a0c66589
To handle all pending timeouts in the context of scheduling a timeout was only necessary because the Timeout framework once made use of the Alarm framework. The method Alarm_scheduler::schedule_absolute took an absolute deadline as argument and we couldn't change this beause the Alarm framework was also used without the Timeout framework. We had to calculate this absolute deadline with the now time of the Timeout framework but the Alarm framework has its own now time that is always a bit behind the one of the Timeout framework. This lead to bad decisisons when finding the right position for the new timeout. Now, we can call schedule_absolute with a relative duration and thereby fix the problem. When we schedule an absolute timeout without considering the small time difference, the end-time for the timeout that is calculated using the local time value is also smaller than the expected end-time. This can also lead to directly triggering timeouts that should have triggered with a certain delay. As it is not trivial to update the local time value while scheduling a timeout _without_ calling other timeout handlers, we simply raise the duration of the new timeout by the age of the local time value. Issue #2704 |
||
|---|---|---|
| .. | ||
| arm | ||
| hw | ||
| duration.cc | ||
| timeout.cc | ||
| timer_connection_time.cc | ||
| timer_connection_timestamp.cc | ||
| timer_connection.cc | ||