From mboxrd@z Thu Jan 1 00:00:00 1970 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) Message-Id: <20050310121124.488cb7c5.pj@engr.sgi.com> In-Reply-To: <1110478613.16432.36.camel@localhost> References: <20050307193938.0935EE594@skynet.csn.ul.ie> <1110239966.6446.66.camel@localhost> <20050310092201.37bae9ba.pj@engr.sgi.com> <1110478613.16432.36.camel@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Dave Hansen Cc: mel@csn.ul.ie, linux-mm@kvack.org, linux-kernel@vger.kernel.org List-ID: 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 1.650.933.1373, 1.925.600.0401 -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: aart@kvack.org