From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Fri, 21 Oct 2005 11:17:06 -0700 From: Paul Jackson Subject: Re: [PATCH 4/4] Swap migration V3: sys_migrate_pages interface Message-Id: <20051021111706.14ba1569.pj@sgi.com> In-Reply-To: References: <20051020225935.19761.57434.sendpatchset@schroedinger.engr.sgi.com> <20051020225955.19761.53060.sendpatchset@schroedinger.engr.sgi.com> <4358588D.1080307@jp.fujitsu.com> <435896CA.1000101@jp.fujitsu.com> <20051021100357.3397269e.pj@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Christoph Lameter Cc: kamezawa.hiroyu@jp.fujitsu.com, Simon.Derr@bull.net, akpm@osdl.org, kravetz@us.ibm.com, linux-kernel@vger.kernel.org, linux-mm@kvack.org, magnus.damm@gmail.com, marcelo.tosatti@cyclades.com List-ID: Christoph wrote: > Therefore if mems_allowed is accessed from outside of the > task then it may not be up to date, right? Yup - exactly. The up to date allowed memory container for a task is in its cpuset, which does have the locking mechanisms needed for safe access from other tasks. The task mems_allowed is just a private cache of the mems_allowed of its cpuset, used for quick access from within the task context by the page allocation code. -- I won't rest till it's the best ... Programmer, Linux Scalability Paul Jackson 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: email@kvack.org