Re: Yielding the processor in a kext?
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com o User A starts the app with 2 threads TA1 and TA2, and this scenario occurs, TA1 is way ahead of TA2, so TA1 lowers is priority. o User B starts the app with only 1 thread TB. --Amanda _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On Sep 7, 2007, at 1:10 PM, Régis Duchesne wrote: Now imagine that 2 different users start 2 different instances of the app: At this point, user A loses: TA1 will almost never be scheduled anymore, because TB will always have a higher priority. I really want to lower the priority of my thread _within_ its task (because the scheduling of that thread relative to the other in the same task is a decision that can be best made by my app). But the APIs that I find only allow me to do it system-wide. So as a workaround, I want a way to yield the processor, i.e. go at the end of the scheduling queue but with the exact same priority.
From this description, I have to ask: why is this all in the kernel? This seems like the type of thing that's much better done in user space. This email sent to site_archiver@lists.apple.com
participants (1)
-
Amanda Walker