On Fri, 3 Aug 2007, Nick Piggin wrote: > > Ok. So MPOL_BIND on a single node. We would have to save the current > > memory policy on the stack and then restore it later. Then you would need > > a special call anyways. > > Well the memory policy will already be set to MPOL_BIND at this point. > The slab allocator I think would just have to honour the node at the > object level.
Who set the policy? The parent process may have its own memory policy. If you set that then the earlier policy is lost. - 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/
