I don't have a copy of POSIX 1003.1 (Realtime Extensions) with me now but if
I remember well this states that sched_yield() should release the CPU to
other threads with the same priority and never schedule task with lower ones.
Now, if for priority We mean static priority the current behaviour of 2.4.x
is correct, but if We mean dynamic priority the current implementation does
not respect the standard.
This coz the goodness() for that task will return -1, and this will make this
process a loser even compared to ones with lower ( dynamic ) priority.
If the POSIX standard concept of priority is nearest to the dynamic one,
probably a better solution would be a move_last_runqueue + clean_yield_flag.
Not that this will change the universe anyway ...
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/