diff options
author | Tejun Heo <tj@kernel.org> | 2009-03-06 14:33:59 +0900 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2009-03-06 14:33:59 +0900 |
commit | edcb463997ed7b2ffa3bac76e3e75957318f2e01 (patch) | |
tree | d1eefb78736404993b0de4a049392f9af578e29e /mm/memory.c | |
parent | 3e24aa58907c62bc79d1094e941a374568f62522 (diff) | |
download | linux-edcb463997ed7b2ffa3bac76e3e75957318f2e01.tar.gz linux-edcb463997ed7b2ffa3bac76e3e75957318f2e01.tar.bz2 linux-edcb463997ed7b2ffa3bac76e3e75957318f2e01.zip |
percpu, module: implement reserved allocation and use it for module percpu variables
Impact: add reserved allocation functionality and use it for module
percpu variables
This patch implements reserved allocation from the first chunk. When
setting up the first chunk, arch can ask to set aside certain number
of bytes right after the core static area which is available only
through a separate reserved allocator. This will be used primarily
for module static percpu variables on architectures with limited
relocation range to ensure that the module perpcu symbols are inside
the relocatable range.
If reserved area is requested, the first chunk becomes reserved and
isn't available for regular allocation. If the first chunk also
includes piggy-back dynamic allocation area, a separate chunk mapping
the same region is created to serve dynamic allocation. The first one
is called static first chunk and the second dynamic first chunk.
Although they share the page map, their different area map
initializations guarantee they serve disjoint areas according to their
purposes.
If arch doesn't setup reserved area, reserved allocation is handled
like any other allocation.
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'mm/memory.c')
0 files changed, 0 insertions, 0 deletions