On 15/04/2015 20:36, Holger Freyther wrote:
>> E.g. rename _gst_signal_at
>> > to _gst_signal_in and then deal with it there? I forgot why we still need
>> > to add the
>> > ClockOnStartupTime to the resumptionTime
> I need to invest if that is scheduling, coalsceling or the cost of disarming,
> arming
> the timer and the signal. but what I see is that
>
> primitive: arg2 1429121982628328000 now 1429121982628320000
> signal_at: 1429121982628328000 now 1429121982628331000
>
> If now > nsTime the deltaMilli will be a huge number and we will sleep a very
> long time. My current preference would be to have a single _gst_get_ns_time
> call to arm these timers and a single comparison.
If now > nsTime, the deltaMilli should be made as small as possible.
The point of using absolute deadline is exactly to match deadlines as
close as possible ("perfect" if the syscall ultimately lets you specify
an absolute deadline). Relative deadlines become less and less accurate
the more load you have, because you can be preempted away between the
computation of the deadline and the setting of the timer.
This is particularly relevant with cooperative multithreading such as
Smalltalk's.
Paolo
_______________________________________________
help-smalltalk mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-smalltalk
