NFC: Update stale comments.

Reviewed by:	alc

2 files changed, 4 insertions, 4 deletions

diff --git a/sys/vm/vm_fault.c b/sys/vm/vm_fault.c
index a1abc44..f1e06d7 100644
--- a/sys/vm/vm_fault.c
+++ b/sys/vm/vm_fault.c
@@ -801,7 +801,7 @@ readrest:
 
 		/*
 		 * To avoid trying to write_lock the map while another process
-		 * has it read_locked (in vm_map_pageable), we do not try for
+		 * has it read_locked (in vm_map_wire), we do not try for
 		 * write permission.  If the page is still writable, we will
 		 * get write permission.  If it is not, or has been marked
 		 * needs_copy, we enter the mapping without write permission,
diff --git a/sys/vm/vm_kern.c b/sys/vm/vm_kern.c
index ca240b1..1cb91c5 100644
--- a/sys/vm/vm_kern.c
+++ b/sys/vm/vm_kern.c
@@ -181,12 +181,12 @@ kmem_alloc(map, size)
 
 	/*
 	 * Guarantee that there are pages already in this object before
-	 * calling vm_map_pageable.  This is to prevent the following
+	 * calling vm_map_wire.  This is to prevent the following
 	 * scenario:
 	 *
 	 * 1) Threads have swapped out, so that there is a pager for the
 	 * kernel_object. 2) The kmsg zone is empty, and so we are
-	 * kmem_allocing a new page for it. 3) vm_map_pageable calls vm_fault;
+	 * kmem_allocing a new page for it. 3) vm_map_wire calls vm_fault;
 	 * there is no page, but there is a pager, so we call
 	 * pager_data_request.  But the kmsg zone is empty, so we must
 	 * kmem_alloc. 4) goto 1 5) Even if the kmsg zone is not empty: when
@@ -194,7 +194,7 @@ kmem_alloc(map, size)
 	 * non-zero data.  kmem_alloc is defined to return zero-filled memory.
 	 *
 	 * We're intentionally not activating the pages we allocate to prevent a
-	 * race with page-out.  vm_map_pageable will wire the pages.
+	 * race with page-out.  vm_map_wire will wire the pages.
 	 */
 	VM_OBJECT_LOCK(kernel_object);
 	for (i = 0; i < size; i += PAGE_SIZE) {