Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ukma!tut.cis.ohio-state.edu!ucbvax!loki.pmel.edsg.hac.COM!suggs
From: suggs@loki.pmel.edsg.hac.COM (Brian Suggs)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Virtual Memory / doable 1.4 request
Message-ID: <8905182025.AA00096@loki.pmel.edsg.hac.com>
Date: 18 May 89 20:25:53 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 32

Matt Dillon writes:
> ... Certainly I would much rather
> have a MEMF_PHYSICAL flag instead of a MEMF_VIRTUAL flag, but it would break
> too many programs ...

My two cents:
It seems that even those advocating MEMF_VIRTUAL agree that MEMF_PHYSICAL is a
better way (exept for maintaining compatability.)

For the benefits of virtual memory to be realized,  MEMF_VIRTUAL *has* to be
the default.  MEMF_PHYSICAL would only be specified for small routines in those
few programs that need it (and you'd better have make sure you really need it!)
What I would like to see in a future version of the OS (1.5? 2.0?) that supports
virtual memory, is a way to invoke a process such that it doesn't use VM nor do
any tasks or processes it invokes.  I think this would be the best way to maintain
compatability with old programs.  And you would only resort to this if the program
didn't work in VM.  At least this way you can try it in VM first!
Then again, if VM isn't part of the official OS until 2.0 (where everythin's
gonna break anyway!) the point becomes moot.
                                                                         
As someone poined out in a previous posting,

        main(){printf("Hello World!\n");}

is a multitasking program on a "proper" multitasking OS.

It should also run in virtual memory *by default*


OK now everyone tell me why I'm wrong...

-Brian                     suggs%loki.pmel.edsg.hac.com@hac2arpa.hac.com