On Fri, Aug 19, 2005 at 08:09:57AM +1000, Amos Shapira wrote: > I'm not sure this is a correct way to measure - gettimeofday(2)'s *interface > definition* is to count nanoseconds, but that doesn't mean that the system's > clock can measure at this resolution.
Don't forget that clock interupts are low priority. On X86 hardware, the lowest. You could very easily miss a clock interupt while a device is busy. That's why x86 clocks often run slow. This is the origin of BOGOMIPS. There were some time critical delays in the kernel and the only way to make sure they were executed properly was to time a specific loop and use that loop for the delay. I have not looked in the kernel for a long time for all I know, they are still there. Geoff. -- Geoffrey S. Mendelson, Jerusalem, Israel [EMAIL PROTECTED] N3OWJ/4X1GM IL Voice: (077)-424-1667 IL Fax: 972-2-648-1443 U.S. Voice: 1-215-821-1838 Support the growing boycott of Google by radio users and hobbyists. It's starting to work, Yahoo has surpassed Google. ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
