Xref: utzoo comp.sys.amiga.misc:2306 comp.sys.amiga.programmer:2331 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!bagate!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.sys.amiga.misc,comp.sys.amiga.programmer Subject: Re: Virtual memory for Amiga! Message-ID: <20391@cbmvax.commodore.com> Date: 5 Apr 91 06:26:59 GMT References: <1991Apr1.222906.12714@jato.jpl.nasa.gov> <1032@cbmger.UUCP> <1991Apr3.114837.1@dev8.mdcbbs.com> Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Organization: Commodore, West Chester, PA Lines: 22 In article <1991Apr3.114837.1@dev8.mdcbbs.com> rivero@dev8.mdcbbs.com writes: >Even with an MMU, the way Amigados structures the free lists in its memory >manager produces accumulating problems with a virtual memory manager, either >in software or hardware. That the memory tends to fragment rapidly has always >been one of the Amigas problems. The tricky part is programs that a) access memory under Forbid or worse yet disable (they may avoid this by only working with their own controller, and not using interrupts (or requiring their use) in the driver); b) programs that put critical code in VM (interrupt handlers, for example). The "proper" method requires programs specify that they want VM and are willing to abide by the rules for safe access. All this was hashed out quite a while ago in c.s.a.tech. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup Disclaimer: Nothing I say is anything other than my personal opinion. Thus spake the Master Ninjei: "To program a million-line operating system is easy, to change a man's temperament is more difficult." (From "The Zen of Programming") ;-)