* Paul Jackson <[email protected]> wrote:
> The tasks we are talking about do -not- want a default RANDOM policy.
> They want node-local allocation for per-thread data (data and stack
> for example), and at the same time spread allocation for kernel space
> (page and slab cache).
ok, i think i got that. Could you perhaps outline two actual use-cases
that would need two cpusets with different policies, on the same box? Or
would you set the spread-out policy for every cpuset that is used in a
box with lots of cpusets, to achieve fairness? (and not bother about it
on boxes with dedicated workloads)
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]
