Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!think!nike!ucbcad!ucbvax!CORY.BERKELEY.EDU!dillon
From: dillon@CORY.BERKELEY.EDU (Matt Dillon)
Newsgroups: net.micro.amiga
Subject: Re: Compatible DOS fixes that would double DOS performance.
Message-ID: <8610142010.AA13654@cory.Berkeley.EDU>
Date: Tue, 14-Oct-86 16:10:42 EDT
Article-I.D.: cory.8610142010.AA13654
Posted: Tue Oct 14 16:10:42 1986
Date-Received: Mon, 20-Oct-86 14:51:49 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: University of California at Berkeley
Lines: 33

>In article <8610120047.AA18469@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>>	(A) Change the sector allocation around directories such that DOS
>>	will attempt to reserve sectors around the Directory node for
>>	File Headers rather than File Data. Currently, small files are
>>	being written on the same track as Directory Nodes.  With
>
>Actually, we need both the directory's node, the file header block, and
>the first sector of the file to be on the same track.
>Unfortunately, this means that they would have to be on the same track as
>the directory, which is on the same track with its junk, with the parent,
>etc.etc.

	Nope, you didn't read my entire article because I addressed this
"problem". 

>The real question is: Is the emphisis on file name expansion (keep file
>headers near directory block, implies directory blocks are not with the
>rest of its directory) or on icon display (keep the first sector of
>data near the file header, and forget about the directory)?
>
>			Michael Gersten
>p.s. Note that (A) does not store all of a directory near the directory's
>node, while (B) stores none of the names near the directory node. You
>can't store all the names by the node as then all the names for the
>entire disk wind up on one track. (B) seems like a fair compromise given
>the file system limits.

	The point is to group them together *somewhere*.  Multiple
track buffering (later in my article), solves most of the problems.  You
could even add a flag settable on a file handle saying "this is a small
file" to give does a little more info on what the hell your doing.

						-Matt