[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Memory allocation

From: Marcus Brinkmann
Subject: Re: Memory allocation
Date: Thu, 11 Apr 2002 09:20:31 -0400
User-agent: Mutt/1.3.25i

On Thu, Apr 11, 2002 at 11:24:01AM +0300, Ognyan Kulev wrote:
> If we use `m*' functions how will we do `vm_copy' and other Mach:isms? 
> (It sounds like masochism, doesn't it? ;-)  It's best to use only one 
> interface that can do all we'd want to -- the `vm_*' functions.  Later 
> we can switch to using something like Kernel Abstraction Layer library. 
> (Farid Hajji names it Virtual Kernel if i recall correctly.)

We changed them to mmap and munmap exactly to get rid of Machism,
in a half-hearted attempt to get microkernel independent.  There is no
way we are going to change it back.

Now, if you really need to use vm_copy, then you might better allocate
the memory with vm_allocate in the first place (not sure, not sure),
but unless you really need you should definitely not use the vm_ calls.

To answer the oter question, yes, we get rid of bcopy etc, usually when
we do other changes to the surrounding code (because it is an update
of minor importance).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]