Path: utzoo!utgpu!attcan!uunet!cs.utexas.edu!sun-barr!apple!oliveb!amiga!jimm
From: jimm@amiga.UUCP (Jim Mackraz)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Virtual Memory
Message-ID: <3863@amiga.UUCP>
Date: 24 May 89 20:05:10 GMT
References: <8905222150.AA05890@jade.berkeley.edu> <10949@behemoth.phx.mcd.mot.com> <6969@cbmvax.UUCP>
Reply-To: jimm@cloyd.UUCP (Jim Mackraz)
Organization: Commodore-Amiga Inc, Los Gatos CA
Lines: 21

In article <6969@cbmvax.UUCP> jesup@cbmvax.UUCP (Randell Jesup) writes:
)	Sorry, but every disk driver I've seen uses tasks, and therefore 
)you MUST break the forbid in order to page, which means a page fault while
)forbidden is disaster.

It's not necessarily a disaster, it's only a disaster if that Forbid() was
protecting a critical operation on data that the disk driver will use.

Certain things will become non-pageable: drivers, their data structures, ...
In making them so, special arbitration can be installed which supplements and
does not depend on Forbid().  And this would by and large be only in "system"
software, which is going to need changes all around anyway.

Now if, on the other hand, that disk operation pops up an AutoRequester, ...

	jimm
-- 
Jim Mackraz, I and I Computing	   	"He's hidden now, but you can see
{cbmvax,well,oliveb}!amiga!jimm          The bubbles where he breathes."
							- Shriekback
Opinions are my own.  Comments are not to be taken as Commodore official policy.