On Tuesday 04 December 2007 11:30, David Schwartz wrote: > Perhaps it might be possible to scan for the task at the same static > priority level that is ready-to-run but last in line among other > ready-to-run tasks and put it after that task?
Nice level versus posix static priority level debate aside, this is the exact behaviour which the compat mode does now basically, when you have all tasks running at nice 0 (which I assume is the essentially the case in both the jvm and firefox tests) (some things, eg. kernel threads or X server could run at a higher prio, but these are not the ones calling yield anyway...) > I think that's about as > close as we can get to the POSIX-specified behavior. I don't think it is a question of POSIX being a bit fuzzy, or some problem we have implementing it. It is explicitly specified to allow any behaviour. So the current default is not wrong, any more than the compat mode is right. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/