Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 11 Sep 2002 13:19:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 11 Sep 2002 13:19:42 -0400 Received: from mailout08.sul.t-online.com ([194.25.134.20]:24711 "EHLO mailout08.sul.t-online.com") by vger.kernel.org with ESMTP id convert rfc822-to-8bit; Wed, 11 Sep 2002 13:18:57 -0400 Content-Type: text/plain; charset=US-ASCII From: Oliver Neukum To: Rik van Riel , Xuan Baldauf Subject: Re: Heuristic readahead for filesystems Date: Wed, 11 Sep 2002 19:20:58 +0200 User-Agent: KMail/1.4.1 Cc: linux-kernel@vger.kernel.org, Reiserfs List References: In-Reply-To: MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT Message-Id: <200209111920.58952.oliver@neukum.name> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 773 Lines: 23 Am Mittwoch, 11. September 2002 18:42 schrieb Rik van Riel: > Your observation is right, but I'm not sure how much it will > matter if we start reading the file at stat() time or at > read() time. > > This is because one disk seek takes about 10 million CPU > cycles on modern systems and we'll have completed the stat(), > open() and started the read() before the disk arm has started > moving ;) Do we gain by sorting the disk accesses ? How about savings due to better cooperation with the IO scheduler? Regards Oliver - 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/