Stephen C. Tweedie:
<snip>
> ..... then the scheduler is required to run them both
> in preference to any background computation.
> Sorry, but in this case you just don't have the option of leaving your
> background task running and scheduling only one of the two runnable
> interactive tasks.
Yes I know that.
Simple question then as at least to me the picture is not clear jet:
How expensive is it to awake the background process and put it on a
_different_ cpu? Will this hurt more than help? Is this tradeoff
balanced enuf for most real world situations?
Micha.
-- -- Michael Schulz, NatS - Uni Hamburg- 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/
This archive was generated by hypermail 2b29 : Mon Jan 31 2000 - 21:00:22 EST