Subject: Re: amap memory allocation
To: YAMAMOTO Takashi <email@example.com>
From: Lars Heidieker <firstname.lastname@example.org>
Date: 07/07/2006 21:47:36
-----BEGIN PGP SIGNED MESSAGE-----
I like that, vmem is really nice. It was build to replace extend etc.
Is it your Idea to use vmem as a backing for the pool allocator and
add some generic pools to replace malloc?
This question just came into my mind as the pool allocator is somehow
used to allocate "virtual address space".
This would bring NetBSD close to what Solaris does with it's vmem/
On 12 Jun 2006, at 04:34, YAMAMOTO Takashi wrote:
>> On Sun, Jun 11, 2006 at 02:45:45PM +0900, YAMAMOTO Takashi wrote:
>>> which includes:
>>> 1. implement solaris-like vmem.
>> Could you elaborate a bit what this is and why you are changing
>> I have no idea what solaris "vmem" is.
> for "what's vmem", see:
> as i wrote in the previous mail, my primary purpose at this point is
> to make amap use kernel_map rather than kmem_map.
> (the latter is more restricted and there's no point for amap to use
> for long term, i'd like to replace extent(9) and malloc(9),
> but my implementation is still far from it.
> YAMAMOTO Takashi
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (Darwin)
-----END PGP SIGNATURE-----