Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!petro!swrinde!ut-sally!im4u!husc6!bloom-beacon!gatech!hubcap!ncrcae!ncr-sd!crash!pnet01!haitex
From: haitex@pnet01.cts.com (Wade Bickel)
Newsgroups: comp.sys.amiga.tech
Subject: Alloc Remember sytems.
Message-ID: <2804@crash.cts.com>
Date: 12 Apr 88 10:17:18 GMT
Sender: news@crash.cts.com
Organization: People-Net [pnet01], El Cajon CA
Lines: 26


    I am writing a fast memory alloc/dealloc system, and have found control
of chip vs. fast memory to be a puzzler.

    Basically, in order to use the system, the programmer must register 
allocation types.  Registration is by mem-type and size and the registration
pointer is used in place of these fields in future requests.
(The registration function returns a pointer).

    The puzzle is how to handle the case where CHIP memory is allocated in
place of FAST memory (ie: No FAST mem. was avail).  This must be fast! 

    If the system is not too idiosyncratic I will make it public by summer.


    Any sugestions/comments welcome,


                                                        Thanks,


                                                                Wade.

UUCP: {cbosgd, hplabs!hp-sdd, sdcsvax, nosc}!crash!pnet01!haitex
ARPA: crash!pnet01!haitex@nosc.mil
INET: haitex@pnet01.CTS.COM