From 68379a6601331ff785d0be4f9c2b6d3114eed3de Mon Sep 17 00:00:00 2001 From: "Thordur I. Bjornsson" Date: Thu, 26 Aug 2010 16:08:25 +0000 Subject: make the comment explaining the kernel submaps a bit better. ok art@, oga@ --- sys/uvm/uvm_km.c | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) (limited to 'sys') diff --git a/sys/uvm/uvm_km.c b/sys/uvm/uvm_km.c index 00a6e23343d..5cb0f619783 100644 --- a/sys/uvm/uvm_km.c +++ b/sys/uvm/uvm_km.c @@ -1,4 +1,4 @@ -/* $OpenBSD: uvm_km.c,v 1.85 2010/07/22 17:31:39 thib Exp $ */ +/* $OpenBSD: uvm_km.c,v 1.86 2010/08/26 16:08:24 thib Exp $ */ /* $NetBSD: uvm_km.c,v 1.42 2001/01/14 02:10:01 thorpej Exp $ */ /* @@ -89,14 +89,15 @@ * up the locking and protection of the kernel address space into smaller * chunks. * - * the vm system has several standard kernel submaps, including: - * kmem_map => contains only wired kernel memory for the kernel - * malloc. *** access to kmem_map must be protected - * by splvm() because we are allowed to call malloc() - * at interrupt time *** - * pager_map => used to map "buf" structures into kernel space - * exec_map => used during exec to handle exec args - * etc... + * The VM system has several standard kernel submaps: + * kmem_map: Contains only wired kernel memory for malloc(9). + * Note: All access to this map must be protected by splvm as + * calls to malloc(9) are allowed in interrupt handlers. + * exec_map: Memory to hold arguments to system calls are allocated from + * this map. + * XXX: This is primeraly used to artificially limit the number + * of concurrent processes doing an exec. + * phys_map: Buffers for vmapbuf (physio) are allocated from this map. * * the kernel allocates its private memory out of special uvm_objects whose * reference count is set to UVM_OBJ_KERN (thus indicating that the objects -- cgit v1.2.3