Messages in this thread | | | Date | Thu, 10 Mar 2005 12:11:24 -0800 | From | Paul Jackson <> | Subject | Re: [PATCH] 0/2 Buddy allocator with placement policy (Version 9) + prezeroing (Version 4) |
| |
Dave wrote: > Perhaps default policies inherited from a cpuset, but overridden by > other APIs would be a good compromise.
Perhaps. The madvise() and numa calls (mbind, set_mempolicy) only affect the current task, as is usually appropriate for calls that allow specification of specific address ranges (strangers shouldn't be messing in my address space). Some external means to set default policy for whole tasks seems to be needed, as well, which could well be via the cpuset.
-- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson <pj@engr.sgi.com> 1.650.933.1373, 1.925.600.0401 - 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/
| |