Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!sri-spam!ames!lll-lcc!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!peter From: peter@sugar.UUCP (Peter da Silva) Newsgroups: comp.sys.amiga Subject: Re: Memory Fragmentation Question Message-ID: <567@sugar.UUCP> Date: Wed, 26-Aug-87 09:01:07 EDT Article-I.D.: sugar.567 Posted: Wed Aug 26 09:01:07 1987 Date-Received: Sat, 29-Aug-87 09:21:33 EDT References: <556489503.138.te07.linesville.ibm032@andrew.cmu.edu> <2074@umn-cs.UUCP> Organization: Sugar Land UNIX - Houston, TX Lines: 31 Summary: Plastics. > [some ninny says he can't think of any problems with fragmentation] > You can't? How about the ability to allocate a hunk of consecutive memory > large enough to run another task? Having 100k of free memory doesn't mean > that you can run a 100k task, since there might be 51 other tasks running, > each with 2K of "free" between them in physical memory. The Amiga, > unfortunately(?) is not a virtual machine. Scatter loading. Except for Aztec 'C' programs in default mode (why does Aztec keep doing this: you can't write a nice, well-behaved, 'C' program without changing a bunch of defaults. Such an ugly wart on such a nice compiler.) programs on the Amiga can scatter-load. Potentially each seperate module can be loaded at a different location. There is a problem: screen and window memory needs to be contiguous... and then of course there's that RAM: 30K ripcord. but program loading shouldn't be a problem. > Wasn't this something we learned in "Computer Science 1001"? I never took CS 1001. Our introductory CS courses were CS1 and CS40. CS1 was in Fortrash with card decks. > As long as we're giving wish lists -- does there exist an equivalent to > UNIX's "kill" for the Amiga? A light skimming of the RKM's doesn't yeild > an easy solution to this problem aching to be answered. Nope. No resource tracking. Ack, oop. -- -- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter -- U <--- not a copyrighted cartoon :->