From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Tue, 6 Mar 2007 07:24:52 -0800 (PST) From: David Rientjes Subject: Re: [RFC} memory unplug patchset prep [0/16] In-Reply-To: <20070306133223.5d610daf.kamezawa.hiroyu@jp.fujitsu.com> Message-ID: References: <20070306133223.5d610daf.kamezawa.hiroyu@jp.fujitsu.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: KAMEZAWA Hiroyuki Cc: Linux-MM , mel@skynet.ie, clameter@engr.sgi.com, akpm@linux-foundation.org List-ID: On Tue, 6 Mar 2007, KAMEZAWA Hiroyuki wrote: > My purpose is to show how memory-unplug can be implemented on ZONE_MOVABLE. > *Any* comments are welcome. This patch just support ia64, which I can test. > If you want me to add arch support, please mail me. > It's great to see progress being made in the memory hot-unplug direction. The implementation seems to be following the plan you had in our coversations from the end of last year. > This patch is a bit old and against 2.6.20-mm2. I'll rebase this and reflect > your comments in the next post (may not soon). > Well booted on ia64 and passed *quick* memory offline test. > When it's rebased, it might be better to apply it to the latest -mm with Mel Gorman's patch series merged. They're in 2.6.21-rc2-mm2. It appears as though you're using a subset of the ZONE_MOVABLE patches as posted from March 1. What about the additional capabilities of ZONE_MOVABLE that aren't included in your patchset, such as allowing hugetlb pages from being allocated under GFP_HIGH_MOVABLE, are going to need to be changed to support memory hot-unplug? Since your patchset wasn't based on the entire ZONE_MOVABLE set, it leads me to believe that some of what it does diverges with the memory hot-unplug use case. Are you aiming to target both ia64 and x86_64 with this patchset or are you focusing on ia64 exclusively at the moment? -- 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