![]() | |||||||||||||
Messages in this thread |
* Paul Jackson <pj@sgi.com> 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-02-06 08:47 [from the cache] ©2003-2008 | |||||||||||||