* Willy Tarreau <[email protected]> wrote:
> scheduler is still a big problem. Not only we occasionally see people
> complaining about unfair CPU distribution across processes (may be
> fixed now), but the scheduler still gives a huge boost to I/O
> intensive tasks which do lots of select() with small time-outs, which
> makes it practically unusable in network-intensive environments. I've
> observed systems on which it was nearly impossible to log in via SSH
> because of this, and I could reproduce the problem locally to create a
> local DoS where a single user could prevent anybody from logging in.
> 2.6.15 has improved a lot on this (pauses have reduced from 35 seconds
> to 4 seconds) but it's still not very good.
i think we've talked about your specific case before, and lets not drop
it on the floor. IIRC you have some special workload (driven by serial
lines?) which behaves interactively and which thus gets too much
boosting.
the passive methods: did you try to mute its impact by renicing it to +5
or +10? If you know that a workload is not interactive, despite it
behaving so, you can always prevent it from getting too much attention.
There's also SCHED_BATCH in 2.6.16-ish kernels.
and there are some active methods as well: you might want to try Mike
Galbraith's scheduler throttling feature:
http://lkml.org/lkml/2006/3/3/59
http://lkml.org/lkml/2006/3/3/63
(which we could try in -mm too perhaps, perhaps Mike has an updated
patch for 2.6.16-rc6-mm1?)
Ingo
-
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]
