> i have left it that way on purpose. There is no reason to assume
> that the timeslice will get smaller after a fork. If we do anything
> like that then we should reset the _parent's_ timeslice ... (thats
> the typical fork() usage pattern: parent forks a child and goes
> sleeping [ie. waiting for results] shortly afterwards).
sounds like it could be abused -- sprinkle your code with losts of
little
if(!fork())
exit();
snippets everywhere -- and you'll end up getting way to much cpu
compared to otehr processes.
-cw
-
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/