Re: [PATCH 1/5] cpuset memory spread basic implementation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ingo wrote:
> in other words: the spreading out likely _hurts_ performance in the 
> typical case (which prefers node-locality), but when you are using 
> multiple cpusets you want to opt for fairness between projects, over 
> opportunistic optimizations such as node-local allocations.

Spreading might be useful for this, but it is not what is driving my
interest in it.

My immediate goal is to obtain spreading across the nodes within of a
single cpuset, running a single job, not "fairness between projects."

I have little interest in cross (between) project memory management
beyond simply isolating them from each other.

-- 
                  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]
  Powered by Linux