Matthew Dillon 64bcb9c815 The swap bitmap allocator was not calculating the bitmap size properly ... in the face of non-stripe-aligned swap areas. The bug could cause a panic during boot. Refuse to configure a swap area that is too large (67 GB or so) Properly document the power-of-2 requirement for SWB_NPAGES. The patch is slightly different then the one Tor enclosed in the P.R., but accomplishes the same thing. PR: kern/20273 Submitted by: Tor.Egge@fast.no		2000-10-13 16:44:34 +00:00
..
default_pager.c
device_pager.c
phys_pager.c
pmap.h
swap_pager.c	The swap bitmap allocator was not calculating the bitmap size properly	2000-10-13 16:44:34 +00:00
swap_pager.h	The swap bitmap allocator was not calculating the bitmap size properly	2000-10-13 16:44:34 +00:00
vm_extern.h
vm_fault.c
vm_glue.c
vm_init.c
vm_kern.c
vm_kern.h
vm_map.c	Convert lockmgr locks from using simple locks to using mutexes.	2000-10-04 01:29:17 +00:00
vm_map.h	For lockmgr mutex protection, use an array of mutexes that are allocated	2000-10-12 22:37:28 +00:00
vm_meter.c	- Add a new process flag P_NOLOAD that marks a process that should be	2000-09-15 22:00:23 +00:00
vm_mmap.c	Add three new VOPs: VOP_CREATEVOBJECT, VOP_DESTROYVOBJECT and VOP_GETVOBJECT.	2000-09-12 09:49:08 +00:00
vm_object.c
vm_object.h
vm_page.c
vm_page.h
vm_pageout.c
vm_pageout.h
vm_pager.c
vm_pager.h
vm_param.h
vm_swap.c	The swap bitmap allocator was not calculating the bitmap size properly	2000-10-13 16:44:34 +00:00
vm_unix.c	If a process is over its resource limit for datasize, still allow	2000-10-06 13:03:50 +00:00
vm_zone.c
vm_zone.h
vm.h
vnode_pager.c
vnode_pager.h