Just can't get enough of that Moose!

[Gary D. Duzan]

=>>    And we should restrict or limit anything with such a drastic impact
=>> on system performance.
=>
=>No. The obvious restriction is not to have virtual memory. If the user wants 
to
=>use more memory then s/he has then s/he pays the price in speed.
=>I don't see any point in providing virtual memory and then saying you can onl
y
=>use it to a certain extant.
=>
   I think we are having a context problem. I'm referring to allocating
physical memory, not virtual memory (which is, I believe, the idea
behind MEM_PHYSICAL.) Allowing unrestricted allocation of physical
memory rather defeats the purpose of virtual memory.

=>>    But if there is only one processor, who is going to release the lock
=>> while you are spinning on it? You would end up spinning until the next
=>> context switch, at least, wasting the rest of the time slice. Of course,
=>
=>Whoops! You're right. (I was using spinlocks last year -- the work WAS on
=>a multiprocessor)
=>
   Well, you're one up on me; I've only read about them.

                                        Gary Duzan
                                        Time  Lord
                                    Third Regeneration
                         Humble Practitioner of the Computer Arts