Subject: Re: Time slices on linux
From: James Platt (james.platt@yale.edu)
Date: Wed Sep 06 2000 - 10:04:55 MDT
Yes, that makes sense. I don't know enough about timing in Linux and Mac
OS but I have had some experience with other kinds of timing issues.
If the MacOS scheduler and the Linux scheduler are operating at different
frequencies, you might have a situation where it is only every 1/10 sec where
they are both at zero at the same time. It could be something like where you
use a video camera which samples at 60 Hz to record a computer monitor which
refreshes at 85 Hz and the result is a flickering effect. The solution would
be to synchronize the timers to the same frequency or a multiple of the same
frequency.
Christian Jaeger wrote:
[stuff deleted]
>
> Hmm, I have another idea now:
>
> Maybe MacOS under mol just has it's own artificial interrupt timer, set at
> 1/60 second or, for mouse pointer movement etc., dependant on cpu time and
> not real time. Now if the perl process is running, mol doesn't get cpu in
> time, or get only half the time slices it would get usually, so the
> interrupt in mol is delayed, and so even if mol *gets* cpu every 30th
> second, the timer hasn't reached zero and so the pointer is still not
> updated.
>
> OK, i'll stop now making weird assumptions
>
> Christian.
This archive was generated by hypermail 2a24 : Wed Sep 06 2000 - 14:06:53 MDT