> > Even if one day we fix the "browsers problem" in the thread > > library, I think this diff will remain necessary to handle > > processes calling sched_yield() in a loop, i.e. processes that are > > spinning. > > > Complete and utter hack: penalize processes or threads on > #system calls/time period. Syscalls are more expensive than > normal execution because of locking which blocks other > processes. Reset the counter when process transitions from > inactive->active.
Yeah..... punish processes when they call the code most likely to be efficient (that is -- kernel code). Thanks for the advice, but you don't have a clue.
