Nick wrote:
> It is somewhat improved. The load balancing will now retry other CPUs,
> but this is pretty costly
Ah - ok. Sounds like a sticky problem.
I am beginning to appreciate Martin's preference for not using
cpus_allowed to pin tasks when load balancing is also needed.
For the big HPC apps that I worry about the most, with hundreds of
parallel, closely coupled threads, one per cpu, we pin all over the
place. But we make very little use of load balancing in that
situation, with one compute bound thread per cpu, humming along for
hours. The scheduler pretty quickly figures out that it has no
useful load balancing to do.
On the other hand, as someone already noted, one can't simulate pinning
to overlapping cpus_allowed masks using overlapping sched domains, as
tasks can just wander off onto someone elses cpu that way.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.925.600.0401
-
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]
