Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1763444AbXESPaa (ORCPT ); Sat, 19 May 2007 11:30:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1758853AbXESPaX (ORCPT ); Sat, 19 May 2007 11:30:23 -0400 Received: from smtp2.linux-foundation.org ([207.189.120.14]:57645 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759275AbXESPaW (ORCPT ); Sat, 19 May 2007 11:30:22 -0400 Date: Sat, 19 May 2007 08:25:04 -0700 From: Andrew Morton To: Fengguang Wu Cc: linux-kernel@vger.kernel.org, Andi Kleen , Jens Axboe , Oleg Nesterov , Steven Pratt , Ram Pai , "linux-ext4@vger.kernel.org" Subject: Re: [PATCH 1/9] readahead: introduce PG_readahead Message-Id: <20070519082504.8baa8d19.akpm@linux-foundation.org> In-Reply-To: <379577826.15160@ustc.edu.cn> References: <20070516224752.500812933@mail.ustc.edu.cn> <379355695.83536@ustc.edu.cn> <20070518232824.9917d794.akpm@linux-foundation.org> <379577826.15160@ustc.edu.cn> X-Mailer: Sylpheed 2.4.1 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1543 Lines: 36 On Sat, 19 May 2007 20:30:31 +0800 Fengguang Wu wrote: > On Fri, May 18, 2007 at 11:28:24PM -0700, Andrew Morton wrote: > > On Thu, 17 May 2007 06:47:53 +0800 Fengguang Wu wrote: > > > > > Introduce a new page flag: PG_readahead. > > > > Is there any way in which we can avoid adding a new page flag? > > > > We have the advantage that if the kernel very occasionally gets the wrong > > result for PageReadahead(page), nothing particularly bad will happen, so we > > can do racy things. > > > > >From a quick peek, it appears that PG_readahead is only ever set against > > non-uptodate pages. If true we could perhaps exploit that: say, > > PageReadahead(page) == PG_referenced && !PG_uptodate? > > PG_uptodate will flip to 1 before the reader touches the page :( OK. > However, it may be possible to share the same bit with PG_reclaim or PG_booked. > Which one would be preferred? I'd like PG_booked to go away too - I don't think we've put that under the microscope yet. If it remains then its scope will be "defined by the filesystem", so readahead shouldn't use it. PG_reclaim belongs to core VFS so that's much better. Let's not do anything ugly, slow or silly in there, but please do take a look, see if there is an opportunity here. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/