Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!bloom-beacon!mit-eddie!bbn!uwmcsd1!ig!agate!ucbvax!decwrl!labrea!polya!rokicki
From: rokicki@polya.Stanford.EDU (Tomas G. Rokicki)
Newsgroups: comp.sys.amiga.tech
Subject: 32-bit memory allocation
Message-ID: <3091@polya.Stanford.EDU>
Date: 21 Jun 88 14:46:25 GMT
Organization: Stanford University
Lines: 20

[ I'm gonna sit by you! ]

In any case, has anyone patched loadseg() to stuff code chunks in
32-bit memory, and rearrange the free memory list so 16-bit memory
gets allocated first?  When I use my system, I use my system, quite
often with multiple huge programs concurrently running, and I'd
much rather have the code execute out of 32-bit memory with the
data come out of 16 (since longwords aren't aligned anyway) than
the reverse.  I'd be interested in any timings people have in this
regard.  Things like vd0: and ram: should *never* get 32-bit memory.

Maybe the stack could be put in 32-bit memory too, but that starts
to get a little messy.

No, I don't have a 68020, but this has nagged me for a while.
-- 
    /-- Tomas Rokicki         ///  Box 2081  Stanford, CA  94309
   / o  Radical Eye Software ///  (TAMU EE '85)   (415) 326-5312
\ /  |  . . . or I       \\\///Join CCFFAALW---Concerned Citzens
 V   |  won't get dressed \XX/Fighting For An Acronym-Less World