Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!ames!ucbcad!ucbvax!renoir.Berkeley.EDU!robinson
From: robinson@renoir.Berkeley.EDU (Michael Robinson)
Newsgroups: comp.sys.amiga
Subject: Track buffers
Message-ID: <19000@ucbvax.BERKELEY.EDU>
Date: Fri, 22-May-87 15:54:32 EDT
Article-I.D.: ucbvax.19000
Posted: Fri May 22 15:54:32 1987
Date-Received: Sat, 23-May-87 16:37:41 EDT
Sender: usenet@ucbvax.BERKELEY.EDU
Reply-To: robinson@renoir.Berkeley.EDU (Michael Robinson)
Distribution: world
Organization: University of California, Berkeley
Lines: 22

.

Well, I've been thinking again (when will I learn my lesson).  What I 
was thinking was that it would be great to have a trackdisk.device that
used up all of available (chip?) ram for track buffers, and released the buffers
on a least recently used basis when memory was allocated (in sort of the
same way that libraries stick around until the memory is needed).

Am I off in left field once again, or is this possible?

Would the .device have to intercept calls to the memory allocator, or is
their a mechanism for non-libraries to find out when memory is needed?


------------------------------------------------------------------------------
         "If you study the logistics and heuristics of the mystics,
          You will find that their minds rarely move in a line"

              "The Ranger isn't going to like it, Yogi."

Mike Robinson                                 USENET:  ucbvax!ernie!robinson
                                              ARPA: robinson@ernie.berkeley.edu