Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 6 Sep 2002 13:28:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 6 Sep 2002 13:28:31 -0400 Received: from dsl-213-023-039-069.arcor-ip.net ([213.23.39.69]:26800 "EHLO starship") by vger.kernel.org with ESMTP id ; Fri, 6 Sep 2002 13:27:58 -0400 Content-Type: text/plain; charset=US-ASCII From: Daniel Phillips To: Anton Altaparmakov , "Peter T. Breuer" Subject: Re: (fwd) Re: [RFC] mount flag "direct" Date: Fri, 6 Sep 2002 19:33:55 +0200 X-Mailer: KMail [version 1.3.2] Cc: Alexander Viro , Xavier Bestel , david.lang@digitalinsight.com, Linux Kernel Mailing List References: 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 Content-Length: 992 Lines: 21 On Friday 06 September 2002 19:20, Anton Altaparmakov wrote: > As of very recently, Andrew Morton introduced an optimization to this with > the get_blocks() interface in 2.5 kernels. Now the file system, when doing > direct_IO at least, returns to the VFS the requested block position _and_ > the size of the block. So the VFS now gains in power in that it only needs > to ask for each block once as it is now aware of the size of the block. > > But still, even with this optimization, the VFS still asks the FS for each > block, and then the FS has to lookup each block. Well, it takes no great imagination to see the progression: get_blocks acts on extents instead of arrays of blocks. Expect to see that around the 2.7 timeframe. -- 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/