Chris Snook wrote:
I don't think Chris's scenario has much bearing on your patch. What he
wants is to have a task that will always be running, but can't
monopolize either CPU. This is useful for certain realtime workloads,
but as I've said before, realtime requires explicit resource
allocation. I don't think this is very relevant to SCHED_FAIR balancing.
I'm not actually using the scenario I described, its just sort of a
worst-case load-balancing thought experiment.
What we want to be able to do is to specify a fraction of each cpu for
each task group. We don't want to have to affine tasks to particular cpus.
This means that the load balancer must be group-aware, and must trigger
a re-balance (possibly just for a particular group) as soon as the cpu
allocation for that group is used up on a particular cpu.
I haven't tried the latest CFS group scheduler patches, so they may
provide the sort of accuracy we're looking for. I'll have to try and
find some time to test them out.
Chris
-
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]
