Re: uvm: remove unused(?) amap_extend

2016-03-27 Thread Mark Kettenis
> Date: Sat, 26 Mar 2016 23:02:52 +0100 > From: Martin Pieuchot > > On 26/03/16(Sat) 19:19, Stefan Kempf wrote: > > Stefan Kempf wrote: > > > amap_extend is called when merging two adjacent areas of virtual address > > > space. However, merging is done only for kernel > > >

Re: uvm: remove unused(?) amap_extend

2016-03-27 Thread Stefan Kempf
Martin Pieuchot wrote: > On 26/03/16(Sat) 19:19, Stefan Kempf wrote: > > Stefan Kempf wrote: > > > amap_extend is called when merging two adjacent areas of virtual address > > > space. However, merging is done only for kernel > > > virtual address space. It's not done for user space: > > > > > >

Re: uvm: remove unused(?) amap_extend

2016-03-26 Thread Martin Pieuchot
On 26/03/16(Sat) 19:19, Stefan Kempf wrote: > Stefan Kempf wrote: > > amap_extend is called when merging two adjacent areas of virtual address > > space. However, merging is done only for kernel > > virtual address space. It's not done for user space: > > > > uvm/uvm_map.c:1359 > > /* > >

Re: uvm: remove unused(?) amap_extend

2016-03-26 Thread Stefan Kempf
Stefan Kempf wrote: > amap_extend is called when merging two adjacent areas of virtual address > space. However, merging is done only for kernel > virtual address space. It's not done for user space: > > uvm/uvm_map.c:1359 > /* >* Try to merge entry. >* >* Userland

uvm: remove unused(?) amap_extend

2016-03-23 Thread Stefan Kempf
amap_extend is called when merging two adjacent areas of virtual address space. However, merging is done only for kernel virtual address space. It's not done for user space: uvm/uvm_map.c:1359 /* * Try to merge entry. * * Userland allocations are kept separated