[EMAIL PROTECTED] (David Woolley) writes: >In article <[EMAIL PROTECTED]>, >Unruh <[EMAIL PROTECTED]> wrote:
>> and the time required to timestamp that packet is about another 2usec, with >> fluctuations depending on whether other interrupts are being serviced. >On both Linux and Windows, interrupt latencies of more than 4ms and >even more than 10ms are quite common. The interrupt processing time I hope you mean 4 or 10usec, not msec. >from the idle loop is not a good indication of the timing on a system >doing real work. (The above figures are based on clock interrupts >overrunning at 250 Hz and 100 Hz clock frequencies, typically when doing >IDE disk I/O.) Although you might not have. The figures I got were on an active machine, although often not used that much. _______________________________________________ questions mailing list questions@lists.ntp.org https://lists.ntp.org/mailman/listinfo/questions
