From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Thu, 17 Jul 2008 10:20:25 -0400 From: Rik van Riel Subject: Re: madvise(2) MADV_SEQUENTIAL behavior Message-ID: <20080717102025.6b7f0e40@cuia.bos.redhat.com> In-Reply-To: <487E628A.3050207@redhat.com> References: <1216163022.3443.156.camel@zenigma> <1216210495.5232.47.camel@twins> <20080716105025.2daf5db2@cuia.bos.redhat.com> <487E628A.3050207@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org Return-Path: To: Chris Snook Cc: Peter Zijlstra , Eric Rannaud , linux-kernel@vger.kernel.org, linux-mm List-ID: On Wed, 16 Jul 2008 17:05:14 -0400 Chris Snook wrote: > > I believe that for mmap MADV_SEQUENTIAL, we will have to do > > an unmap-behind from the fault path. Not every time, but > > maybe once per megabyte, unmapping the megabyte behind us. > > > > That way the normal page cache policies (use once, etc) can > > take care of page eviction, which should help if the file > > is also in use by another process. > > Wouldn't it just be easier to not move pages to the active list when > they're referenced via an MADV_SEQUENTIAL mapping? You want to check the MADV_SEQUENTIAL hint at pageout time and discard the referenced bit from the pte? > If we keep them on the inactive list, they'll be candidates for > reclaiming Only if we ignore the referenced bit. Which I guess we can do. -- All Rights Reversed -- 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