From owner-freebsd-fs Wed Oct 2 08:23:04 1996 Return-Path: owner-fs Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id IAA15053 for fs-outgoing; Wed, 2 Oct 1996 08:23:04 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA15047; Wed, 2 Oct 1996 08:23:00 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.7.5/8.6.9) id KAA01068; Wed, 2 Oct 1996 10:22:16 -0500 (EST) From: John Dyson Message-Id: <199610021522.KAA01068@dyson.iquest.net> Subject: Re: vnode and cluster read-ahead To: dg@Root.COM Date: Wed, 2 Oct 1996 10:22:16 -0500 (EST) Cc: heo@cslsun10.sogang.ac.kr, freebsd-hackers@freebsd.org, freebsd-fs@freebsd.org In-Reply-To: <199610021452.HAA07229@root.com> from "David Greenman" at Oct 2, 96 07:52:03 am Reply-To: dyson@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-fs@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Even if we did want to change it, there really isn't a way to do what > you're suggesting above - you don't have access to the file struct at the > level that the clustering decision is made. You'd have to change the code > to propagate clustering hints from the read/write system calls. Yuck. > I actually thought about doing it (and may have discussed it with you, David), and I think that was my conclusion also. The existing interfaces don't convieniently support it. John