Re: kmem_alloc replacement in Tiger
Re: kmem_alloc replacement in Tiger
- Subject: Re: kmem_alloc replacement in Tiger
- From: Nikita Danilov <email@hidden>
- Date: Thu, 2 Feb 2006 01:38:35 +0300
Terry Lambert writes:
[...]
> Likewise, at least with FreeBSD's unified VM and buffer cache, and in
> NetBSD's case, their UVM implementation, and Windows, it's also likely
> better to avoid the possibility of fragmentation of the kernel virtual
> address map, even if it's a full 64 bits. The main issue is the
> number of pmap entries needed to support that large an address space
> grows as the address space becomes fragmented, even if the amount of
> available physical memory is relatively small. I believe this will
> also be a problem on Linux, unless something happened very recently to
> change things there; it may or may not be a problem on Solaris,
In overwhelming majority of cases Linux uses 1:1 mapping of physical to
virtual memory in the kernel mode, and kernel `pmap' is modified quite
rarely. All major memory consumers (file system, anonymous memory, slab
allocator) work in 1:1 mode.
Nikita.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden