Subject: Re: kernel wired pages
To: None <tech-kern@netbsd.org>
From: YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>
List: tech-kern
Date: 01/16/2005 16:04:46
hi,
> is there any reason to use uvm object and managed mappings for
> wired portions of kernel, like buffer cache and nointr pool backend?
> if no reason, i'd like to change it because:
> - it wastes resources like pv_entry.
> - it confuses uvm page type balancing. (PR/27030)
- and it complicates bootstrap.
i'll change uvm_km_* functions like the following, if no one objects.
- uvm_km_kmemalloc/uvm_km_kmemfree
allocate/free wired kernel memory.
- uvm_km_valloc/uvm_km_vfree
allocate/free pagable memory backed by kernel_object.
- uvm_km_kvaalloc/uvm_km_kvafree
allocate/free a kva range.
- introduce new flags, UVM_KMF_WAITVA, UVM_KMF_ZERO.
- remove uvm_km_alloc, uvm_km_zalloc, uvm_km_free, uvm_km_valloc_*.
YAMAMOTO Takashi