while creating the patch I promised in my last message, I
stumbled across a strange bloat in sys_sched_yield().
In the function I come across a move_last_runqueue(current),
but AFAIK that shouldn't have any influence on the performance
of the function at all -- the scheduler will be walking the
whole run queue anyway...
Apart from that, I wonder if the whole locking business
in the function is needed; the only thing we do is
modify current->policy and set current->need_resched.
And even _if_ somebody tampered with current->policy
while we weren't looking (sys_set_scheduler()) it
shouldn't matter in this case.
Another improvement for Richard and Larry :)
Rik.
+-------------------------------------------------------------------+
| Linux memory management tour guide. H.H.vanRiel@phys.uu.nl |
| Scouting Vries cubscout leader. http://www.phys.uu.nl/~riel/ |
+-------------------------------------------------------------------+
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/