> I've been trialling a new load module for the contest benchmark
> (http://contest.kolivas.net) which simply forks a process that does
> nothing, waits for it to die, then repeats. Here are the results I have
> obtained so far:
> fork_load:
> Kernel Time CPU Ratio
> 2.4.19 100.05 69% 1.37
> 2.4.19-ck7 74.65 95% 1.02
> 2.5.38 77.35 95% 1.06
> 2.5.38-mm2 76.99 95% 1.06
>
> ck7 uses O1, preempt, low latency
Looks like the O(1) scheduler has a problem, then. The continuous
fork() loop should get 20% of the CPU, not 5%.
regards,
Rik
-- Bravely reimplemented by the knights who say "NIH".http://www.surriel.com/ http://distro.conectiva.com/
Spamtraps of the month: september@surriel.com trac@trac.org
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/