Path: utzoo!attcan!uunet!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Task KILL for Amiga
Message-ID: <5755@cbmvax.UUCP>
Date: 23 Jan 89 08:07:04 GMT
References: <3716@crash.cts.com> <10908@s.ms.uky.edu> <5713@cbmvax.UUCP> <10926@s.ms.uky.edu> <5748@cbmvax.UUCP> <10939@s.ms.uky.edu>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 30

In article <10939@s.ms.uky.edu> sean@ms.uky.edu (Sean Casey) writes:
>Ok so the reason resources aren't being tracked is because:
>
>1. Resource passing makes it too complicated.
>2. Memory is allocated in very small chunks.
>3. There are many resources.
>4. It wasn't written into the system.
>5. Nasty programs can make recovery impossible.
>
>These don't seem like insurmountable obstacles, except possibly for the
>last. Consider running Amigados on an MMUed machine. Then #5 would be
>no problem at all. That's the biggest reason I'd like to see resource
>tracking; taking advantage of an MMU.

	Well, add not enough programmer time for why they're not being
tracked currently.  Big roadblock (big job) :-(

	A protected system would help with #5, except that the system wasn't
designed for an MMU either, and depends HIGHLY on shared memory for its
design and response speed.  Many programs would break, even "correctly"
written programs, probably.  Remember, if anyone might need to look at
memory you allocate, use MEMF_PUBLIC - and don't allocate such things as
globals/statics in your program, since it may not be public.  That will at
least help a little if we go to an MMU system.

	Note that we only just started selling the first amiga with an
MMU, 99.9+% don' have them.

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup