kern/slab: directmap update

The main impact of the direct physical mapping on the kmem module is the
slab size computation. The page allocator requires the allocation size
to be a power-of-two above the page size since it uses the buddy memory
allocation algorithm.

Custom slab allocation functions are no longer needed since the only
user was the kentry area, which has been removed recently.

The KMEM_CACHE_NOCPUPOOL flag is also no longer needed since CPU pools,
which are allocated from a kmem cache, can now always be allocated out
of the direct physical mapping.

1 files changed, 14 insertions, 10 deletions

diff --git a/vm/vm_external.c b/vm/vm_external.c
index 2e2593b..03ebcfb 100644
--- a/vm/vm_external.c
+++ b/vm/vm_external.c
@@ -137,14 +137,18 @@ void		vm_external_module_initialize(void)
 {
 	vm_size_t	size = (vm_size_t) sizeof(struct vm_external);
 
-	kmem_cache_init(&vm_external_cache, "vm_external", size, 0,
-			NULL, NULL, NULL, 0);
-
-	kmem_cache_init(&vm_object_small_existence_map_cache,
-			"small_existence_map", SMALL_SIZE, 0,
-			NULL, NULL, NULL, 0);
-
-	kmem_cache_init(&vm_object_large_existence_map_cache,
-			"large_existence_map", LARGE_SIZE, 0,
-			NULL, NULL, NULL, 0);
+	kmem_cache_init (&vm_external_cache,
+                 "vm_external",
+                 size, 0,
+                 NULL, 0);
+
+	kmem_cache_init (&vm_object_small_existence_map_cache,
+                 "small_existence_map",
+                 SMALL_SIZE, 0,
+                 NULL, 0);
+
+	kmem_cache_init (&vm_object_large_existence_map_cache,
+                 "large_existence_map",
+                 LARGE_SIZE, 0,
+                 NULL, 0);
 }