Re: windows = realtime?

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Pat B (spam_at_ftc.gov)
Date: 07/10/04 

Date: Sat, 10 Jul 2004 05:08:26 GMT

but 20 milliseconds! that's insanely bad.

Mike Powers wrote:
> The physical interrupts are prioritized. If you get two or more
> interrupts at the same time, one will be handled first.
>
> Pat B wrote:
>
>> Nope, these are _interrupt_ latencies. To my device drivers ISR().
>> Something else in the system held off interrupts to my PCI device for
>> 20-24 millseconds about four times a day.
>>
>>>> I'm experiencing interrupts latencies of 20 milliseconds on
>>>> some machines. More often than not you should be able to go
>>>> sub-millisecond, but there are no guarantees on this OS.
>>>> Some vendors just get their device drivers working and don't
>>>> worry about the huge latency problems.
>>>>

Relevant Pages

  • Re: All RTOS (linux Based ) Other than RT-Linux
    ... priorities, no swapping, task activation/resumption on specified interrupts, ... extensions are more than adequate for the average process control or SCADA ... a task every 5 milliseconds one does not exit and request reactivation in the ...
    (comp.os.linux.setup)
  • Re: windows = realtime?
    ... but 20 milliseconds! ... Mike Powers wrote: ... > The physical interrupts are prioritized. ... > interrupts at the same time, ...
    (microsoft.public.windowsxp.device_driver.dev)
  • Re: windows = realtime?
    ... but 20 milliseconds! ... Mike Powers wrote: ... > The physical interrupts are prioritized. ... > interrupts at the same time, ...
    (microsoft.public.win32.programmer.kernel)
  • Re: Latency traces I cannot interpret (sa1100, 2.6.15-rc7-rt1)
    ... >> Interrupts seem to be blocked for milliseconds, ... there are console-related function names ... > interrupts, or there's a bug in the latency tracer. ...
    (Linux-Kernel)