On Friday 07 April 2006 19:38, Mike Galbraith wrote:
> Greetings,
>
> Problem: Wake-up -> cpu latency increases with the number of runnable
> tasks, ergo adding this latency to sleep_avg becomes increasingly potent
> as nr_running increases. This turns into a very nasty problem with as
> few as 10 httpd tasks doing round robin scheduling. The result is that
> you can only login with difficulty, and interactivity is nonexistent.
>
> Solution: Restrict the amount of boost a task can receive from this
> mechanism, and disable the mechanism entirely when load is high. As
> always, there is a price for increasing fairness. In this case, the
> price seems worth it. It bought me a usable 2.6 apache server.
Since this is an RFC, here's my comments :)
This mechanism is designed to convert on-runqueue waiting time into sleep. The
basic reason is that when the system is loaded, every task is fighting for
cpu even if they only want say 1% cpu which means they never sleep and are
waiting on a runqueue instead of sleeping 99% of the time. What you're doing
is exactly biasing against what this mechanism is in place for. You'll get
the same effect by bypassing or removing it entirely. Should we do that
instead?
-ck
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
