From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx140.postini.com [74.125.245.140]) by kanga.kvack.org (Postfix) with SMTP id A27AD6B0083 for ; Tue, 15 May 2012 10:27:52 -0400 (EDT) Date: Tue, 15 May 2012 09:27:47 -0500 (CDT) From: Christoph Lameter Subject: Re: Allow migration of mlocked page? In-Reply-To: Message-ID: References: <4FAC9786.9060200@kernel.org> <20120511131404.GQ11435@suse.de> <4FADA007.3020309@gmail.com> <20120514133210.GE29102@suse.de> <1337003515.2443.35.camel@twins> <1337004860.2443.47.camel@twins> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org List-ID: To: Roland Dreier Cc: Peter Zijlstra , Mel Gorman , KOSAKI Motohiro , Minchan Kim , Johannes Weiner , Rik van Riel , Andrew Morton , Andrea Arcangeli , KAMEZAWA Hiroyuki , "linux-mm@kvack.org" , tglx@linutronix.de, Ingo Molnar , Theodore Ts'o On Mon, 14 May 2012, Roland Dreier wrote: > In any case I don't see any problem with doing vma splitting in > drivers/core/infiniband/umem.c if need be. Prohibiting migration is already supported at the VMA level. There is no need to add anyting extra. "struct vm_operations_struct" has a field for the "migrate" function. If that field is set to "fail_migrate_page" then no migration will ever take place on the VMA. But this feature is not accessible from user space. So far it has only been used by special filesystesm. And disabling migration does not solve the "I want no faults whatsovever" requirement that I keep hearing. -- 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/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org