From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from zps75.corp.google.com (zps75.corp.google.com [172.25.146.75]) by smtp-out.google.com with ESMTP id l9PKACUF011800 for ; Thu, 25 Oct 2007 13:10:12 -0700 Received: from nf-out-0910.google.com (nfhf5.prod.google.com [10.48.233.5]) by zps75.corp.google.com with ESMTP id l9PK9asg013388 for ; Thu, 25 Oct 2007 13:10:11 -0700 Received: by nf-out-0910.google.com with SMTP id f5so473391nfh for ; Thu, 25 Oct 2007 13:10:11 -0700 (PDT) Message-ID: Date: Thu, 25 Oct 2007 16:10:11 -0400 From: "Ross Biro" Subject: Re: RFC/POC Make Page Tables Relocatable In-Reply-To: <1193342419.24087.71.camel@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <1193330774.4039.136.camel@localhost> <1193335725.24087.19.camel@localhost> <1193340182.24087.54.camel@localhost> <1193342419.24087.71.camel@localhost> Sender: owner-linux-mm@kvack.org Return-Path: To: Dave Hansen Cc: linux-mm@kvack.org, Mel Gorman List-ID: On 10/25/07, Dave Hansen wrote: > How would it get freed? > The process exists or ummaps the range of memory. The relocation code is likely called on a different cpu in the node and currently has no way to pin the data in memory. Perhaps finding a way to pin the page would help the other locking issues, so it might solve lots of problems. Ross -- 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