🚀 go-pugleaf

In article <dej.01pt@qpoint.ocunix.on.ca> dej@qpoint.ocunix.on.ca (David Jones) writes:
>Does it work if I Forbid() and then page fault?  Disable() and page fault?
>(i.e. if my Forbid() gets broken and whatever I was trying to mutex with
>the Forbid() gets un-mutexed, then it don't work.)

GigaMem tries its best to keep Forbid()s mutex. This is nevertheless
100%, one could figure configurations where another task could sneak
in and change some lists etc.
Disable() does not work and will provoke a software failure-like requester
giving the user the ability to Suspend/Reboot...

Note: Both this cases could be avoided for existing software due to
GigaMem's unique feature to use program specific settings..
Even for 'nasty' programs like ImageMaster which uses MEMF_PUBLIC for
ALL his buffer allocations.

>I've heard of GigaMem, but I'd be interested in seeing exactly what
>restrictions are placed on programmers because of it.  I am writing a
>shared library, and I don't want to deny appliction programmers use of
>my library if they want to use GigaMem.

I try to put this as short as possible:
1) Use MEMF_PUBLIC for all allocations except the large (and probably
   growing with the data) buffers. 
2) Not these large buffers from within Disable()/SoftInts/IntHandlers
   and preferably not Forbid(). Don't put  program code into such buffers.

Note: Point 1 is a hint, point 2 is a general rule for virtual memory...

More complete information can be obtained from the GigaMem developer
kit which includes information about vmem.library and its support routines
and can be obtained from the distributor of GigaMem.

- Chris
-- 
-- 
Chris Schneider - cschneid@amiga.physik.unizh.ch BIX: hschneider IRC: cschneid
It's impossible to enjoy idling thoroughly unless one has plenty of work to do