diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2018-07-21 23:48:51 +0300 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2018-07-21 23:48:51 +0300 |
commit | 3928d4f5ee37cdc523894f6e549e6aae521d8980 (patch) | |
tree | c328fd919e48fc8442db04d13c2ba1fe2c0f88e4 /include/linux/yam.h | |
parent | 191a3afa98b857faf5231981ddbab66698034273 (diff) | |
download | linux-3928d4f5ee37cdc523894f6e549e6aae521d8980.tar.xz |
mm: use helper functions for allocating and freeing vm_area structs
The vm_area_struct is one of the most fundamental memory management
objects, but the management of it is entirely open-coded evertwhere,
ranging from allocation and freeing (using kmem_cache_[z]alloc and
kmem_cache_free) to initializing all the fields.
We want to unify this in order to end up having some unified
initialization of the vmas, and the first step to this is to at least
have basic allocation functions.
Right now those functions are literally just wrappers around the
kmem_cache_*() calls. This is a purely mechanical conversion:
# new vma:
kmem_cache_zalloc(vm_area_cachep, GFP_KERNEL) -> vm_area_alloc()
# copy old vma
kmem_cache_alloc(vm_area_cachep, GFP_KERNEL) -> vm_area_dup(old)
# free vma
kmem_cache_free(vm_area_cachep, vma) -> vm_area_free(vma)
to the point where the old vma passed in to the vm_area_dup() function
isn't even used yet (because I've left all the old manual initialization
alone).
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/yam.h')
0 files changed, 0 insertions, 0 deletions