From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Wed, 2 Jul 2003 14:05:49 -0400 (EDT) From: Rik van Riel Subject: Re: What to expect with the 2.6 VM In-Reply-To: <20030702174700.GJ23578@dualathlon.random> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-mm@kvack.org Return-Path: To: Andrea Arcangeli Cc: "Martin J. Bligh" , Mel Gorman , Linux Memory Management List , Linux Kernel Mailing List List-ID: On Wed, 2 Jul 2003, Andrea Arcangeli wrote: > So ether we declare 32bit archs obsolete in production with 2.6, or we > drop rmap behind remap_file_pages. > Something has to change since IMHO in the current 2.5.73 remap_file_pages > is nearly useless. Agreed. What we did for a certain unspecified kernel tree at Red Hat was the following: 1) limit sys_remap_file_pages functionality to shared memory segments on ramfs (unswappable) and tmpfs (mostly unswappable;)) 2) have the VMAs with remapped pages in them marked VM_LOCKED 3) do not set up pte chains for the pages that get mapped with install_page 4) remove said pages from the LRU list, in the ramfs case, they're unswappable anyway so we shouldn't have the VM scan them The only known user of sys_remap_file_pages was more than happy to have the functionality limited to just what they actually need, in order to get simpler code with less overhead. Lets face it, nobody is going to use sys_remap_file_pages for anything but a database shared memory segment anyway. You don't need to care about truncate or the other corner cases. -- 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: aart@kvack.org