From owner-cvs-sys Sat Nov 30 14:41:56 1996 Return-Path: owner-cvs-sys Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10706 for cvs-sys-outgoing; Sat, 30 Nov 1996 14:41:56 -0800 (PST) Received: (from dyson@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id OAA10690; Sat, 30 Nov 1996 14:41:51 -0800 (PST) Date: Sat, 30 Nov 1996 14:41:51 -0800 (PST) From: John Dyson Message-Id: <199611302241.OAA10690@freefall.freebsd.org> To: CVS-committers, cvs-all, cvs-sys Subject: cvs commit: src/sys/sys buf.h param.h src/sys/vm vm_fault.c vm_map.c vm_map.h vm_pager.c src/sys/kern vfs_bio.c vfs_cluster.c Sender: owner-cvs-sys@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk dyson 96/11/30 14:41:50 Modified: sys/sys buf.h param.h sys/kern vfs_bio.c vfs_cluster.c sys/vm vm_fault.c vm_map.c vm_map.h vm_pager.c Log: Implement a new totally dynamic (up to MAXPHYS) buffer kva allocation scheme. Additionally, add the capability for checking for unexpected kernel page faults. The maximum amount of kva space for buffers hasn't been decreased from where it is, but it will now be possible to do so. This scheme manages the kva space similar to the buffers themselves. If there isn't enough kva space because of usage or fragementation, buffers will be reclaimed until a buffer allocation is successful. This scheme should be very resistant to fragmentation problems until/if the LFS code is fixed and uses the bogus buffer locking scheme -- but a 'fixed' LFS is not likely to use such a scheme. Now there should be NO problem allocating buffers up to MAXPHYS. Revision Changes Path 1.35 +3 -1 src/sys/sys/buf.h 1.17 +3 -6 src/sys/sys/param.h 1.107 +80 -20 src/sys/kern/vfs_bio.c 1.39 +9 -1 src/sys/kern/vfs_cluster.c 1.58 +7 -8 src/sys/vm/vm_fault.c 1.58 +6 -1 src/sys/vm/vm_map.c 1.16 +4 -3 src/sys/vm/vm_map.h 1.25 +20 -13 src/sys/vm/vm_pager.c