From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 13 Apr 2006 18:33:07 -0700 (PDT) From: Christoph Lameter Subject: Re: [PATCH 5/5] Swapless V2: Revise main migration logic In-Reply-To: <20060414101959.d59ac82d.kamezawa.hiroyu@jp.fujitsu.com> Message-ID: References: <20060413235406.15398.42233.sendpatchset@schroedinger.engr.sgi.com> <20060413235432.15398.23912.sendpatchset@schroedinger.engr.sgi.com> <20060414101959.d59ac82d.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: akpm@osdl.org, hugh@veritas.com, linux-kernel@vger.kernel.org, lee.schermerhorn@hp.com, linux-mm@kvack.org, taka@valinux.co.jp, marcelo.tosatti@cyclades.com List-ID: On Fri, 14 Apr 2006, KAMEZAWA Hiroyuki wrote: > For hotremove (I stops it now..), we should fix this later (if we can do). > If new SWP_TYPE_MIGRATION swp entry can contain write protect bit, > hotremove can avoid copy-on-write but things will be more complicated. This is a known issue.I'd be glad if you could come up with a working scheme to solve this that is simple. -- 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