On Fri, 26 Oct 2007, Paul Jackson wrote: > Choice B lets the task calculate its mempolicy mask as if it owned > the entire system, and express whatever elaborate mempolicy placement > it might need, when blessed with enough memory nodes to matter. > The system would automatically scrunch that request down to whatever > is the current size and placement of the cpuset holding that task. > > Given a clean slate, I prefer Choice B.
Yes. We should default to Choice B. Add an option MPOL_MF_RELATIVE to enable that functionality? A new version of numactl can then enable that by default for newer applications. - 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/
