diff options
| author | Richard Braun <rbraun@sceen.net> | 2014-12-10 21:52:40 +0100 |
|---|---|---|
| committer | Justus Winter <4winter@informatik.uni-hamburg.de> | 2015-08-15 12:43:27 +0200 |
| commit | f070e81f33c7f01a70923782b5358d014712d9ef (patch) | |
| tree | 8ceb5b8852c111558d394b002d71fc34bc421996 /vm/vm_object.c | |
| parent | 0b0d06c34589595cec2bea6f9b55b8e9ae51c3cf (diff) | |
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.
Diffstat (limited to 'vm/vm_object.c')
| -rw-r--r-- | vm/vm_object.c | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/vm/vm_object.c b/vm/vm_object.c index b403d30..ee09e3b 100644 --- a/vm/vm_object.c +++ b/vm/vm_object.c @@ -259,8 +259,10 @@ vm_object_t vm_object_allocate( */ void vm_object_bootstrap(void) { - kmem_cache_init(&vm_object_cache, "vm_object", - sizeof(struct vm_object), 0, NULL, NULL, NULL, 0); + kmem_cache_init (&vm_object_cache, + "vm_object", + sizeof(struct vm_object), 0, + NULL, 0); queue_init(&vm_object_cached_list); vm_object_cache_lock_init(); |