Timing issue with Dummynet on high kernel timer interrupt

Adrian Chadd adrian.chadd at gmail.com
Fri Nov 6 21:15:51 UTC 2015


On 6 November 2015 at 12:58, Ian Lepore <ian at freebsd.org> wrote:
> On Fri, 2015-11-06 at 11:15 -0800, Adrian Chadd wrote:
>> Ideally there'd be both behaviours:
>>
>> * You'd specify whether a timer/sleep needs to be exact or can
>> withstand some jitter (which is what linux provides); and
>> * You can communicate to the kernel its aggressiveness for coalescing
>> wakeups.
>>
>
> We already implement exactly both of these things (the former in args
> to scheduling callouts, the latter in the form of the sysctl I
> referenced earlier which lets you set the "agressivness for
> coalescing").
>
> The problem with the former is very little code actually uses the
> flavor of callout scheduling that lets you specify precision.  The
> problem with the latter is that its default value is to allow enough
> deviation that people think the system is misbehaving.

Right. What about sleep, though? (eg userland calling sleep, usleep, etc.)

Would the original poster problem be fixed just by setting the exact precision?

-adrian


More information about the freebsd-net mailing list