site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Am 29.09.2004 um 15:54 schrieb John Siracusa: This is how I understand things but again, I'm no expert :-) Markus - - - - - - - - - - - - - - - - - - - Dipl. Ing. Markus Hitter http://www.jump-ing.de/ _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... One theory presented to explain the results was that the kernel is taking CPU temperature into account when doling out CPU cycles. Well, I'm not really a kernel expert, but the scheduler's task is to decide which process/thread gets the next CPU quantum, where a CPU quantum is about 10 ms. If there's no process in need of processing time, it sends the CPU into doze mode. I thought it might be the CPU hog "punisher" in the kernel Surely, there are more mechanisms going on in the kernel, independent from the scheduler. If the CPU supports running at different speeds, you should be able to switch between them without telling the scheduler. This email sent to site_archiver@lists.apple.com