Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 6 Feb 2002 04:02:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 6 Feb 2002 04:02:44 -0500 Received: from dsl-213-023-043-188.arcor-ip.net ([213.23.43.188]:15793 "EHLO starship.berlin") by vger.kernel.org with ESMTP id ; Wed, 6 Feb 2002 04:02:33 -0500 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: Rik van Riel , Pavel Machek Subject: Re: [PATCH] Radix-tree pagecache for 2.5 Date: Wed, 6 Feb 2002 10:07:02 +0100 X-Mailer: KMail [version 1.3.2] Cc: Jeff Garzik , , In-Reply-To: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On February 5, 2002 07:45 pm, Rik van Riel wrote: > On Tue, 5 Feb 2002, Pavel Machek wrote: > > > > > the biggest reason for this is that we *suck* at readahead for > > > > > mmap.... > > > > > > > > Is there not also fault overhead and similar issues related to mmap(2) > > > > in general, that are not present with read(2)/write(2)? > > > > > > If a fault is more expensive than a system call, we're doing > > > something wrong in the page fault path ;) > > > > You can read 128K at a time, but you can't fault 128K... > > Why not ? > > If the pages are present (read-ahead) and the page table > is present, I see no reason why we couldn't fill in 32 > page table entries at once. Yes, essentially what you want is to schedule a generic_file_readahead, which we'd need to cook up a mechanism for doing. The other part - much harder - is deciding when to readahead, and how much. I'd amend your original statement to just 'we *suck* at readahead'. -- Daniel - 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/