From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 19 Sep 2006 14:28:10 -0700 (PDT) From: Christoph Lameter Subject: Re: [PATCH] GFP_THISNODE for the slab allocator In-Reply-To: Message-ID: References: <20060914220011.2be9100a.akpm@osdl.org> <20060914234926.9b58fd77.pj@sgi.com> <20060915002325.bffe27d1.akpm@osdl.org> <20060916044847.99802d21.pj@sgi.com> <20060916083825.ba88eee8.akpm@osdl.org> <20060916145117.9b44786d.pj@sgi.com> <20060916161031.4b7c2470.akpm@osdl.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: David Rientjes Cc: Andrew Morton , Paul Jackson , linux-mm@kvack.org List-ID: On Tue, 19 Sep 2006, David Rientjes wrote: > If the memory from existing nodes are used to create the new node, then > any tasks assigned to that parent node through cpusets will be degraded. > Not a problem since the user would be aware of this affect on node > creation, but you'd need callback_mutex and task_lock for each task > within the parent node and possibly rcu_read_lock for the mems_generation. Paul has already cpuset code in mm that supports exactly this situation. He can probably explain the locking which as far as I can tell is much simpler than you anticipate. -- 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