Messages in this thread | | | Subject | Re: [PATCH] Dynamic tick, version 050127-1 | From | Eric St-Laurent <> | Date | Tue, 01 Feb 2005 20:06:51 -0500 |
| |
On Tue, 2005-02-01 at 15:20 -0500, Lee Revell wrote:
> I was wondering how Windows handles high res timers, if at all. The > reason I ask is because I have been reverse engineering a Windows ASIO > driver, and I find that if the latency is set below about 5ms, by
By default, Windows "multimedia" timers have 10ms resolution (this depends on the exact version of Windows used...). You can call the timeBeginPeriod() function to lower the resolution to 1ms.
This resolution seem related to the task scheduler timeslice. After you call this function, the Sleep() call has also a resolution of 1ms instead of 10ms.
I remember reading that the multimedia timers are implemented as a high priority thread.
You can found more details on this site :
http://www.geisswerks.com/ryan/FAQS/timing.html
Best regards,
Eric St-Laurent
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |