Hi,
On Fri, 28 Jan 2000 10:18:16 +0100,
michael_schulz@public.uni-hamburg.de said:
>> xosview is scheduled. You just invalidated your experiment at that
>> point
> What about cpu0: xosview, cpu1: tight loop and they stay where they
> are? The scheduler was written in order to exactly do that, but
> somehow it doesn't. Why?
Umm, what CPU is X going to run on in that case?
You have two high-priority, interactive tasks to be scheduled: X and
xosview. You have one low-priority background task --- the
benchmark. If both xosview and X are ever runnable at the same time,
then the benchmark task MUST be bumped off the cpu. And if the other
cpu becomes free first, then what are you going to do? Leave it idle?
That may win in some cases but in general it's a bad idea to bet that
way.
--Stephen
-
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:21 EST