diff options
| author | Benjamin Herrenschmidt | 2010-07-07 00:39:01 +0200 |
|---|---|---|
| committer | Benjamin Herrenschmidt | 2010-08-05 04:56:07 +0200 |
| commit | e63075a3c9377536d085bc013cd3fe6323162449 (patch) | |
| tree | 28fde124dde6df867947882fc686d228502846df /arch/sh/include | |
| parent | memblock: Expose MEMBLOCK_ALLOC_ANYWHERE (diff) | |
| download | kernel-qcow2-linux-e63075a3c9377536d085bc013cd3fe6323162449.tar.gz kernel-qcow2-linux-e63075a3c9377536d085bc013cd3fe6323162449.tar.xz kernel-qcow2-linux-e63075a3c9377536d085bc013cd3fe6323162449.zip | |
memblock: Introduce default allocation limit and use it to replace explicit ones
This introduce memblock.current_limit which is used to limit allocations
from memblock_alloc() or memblock_alloc_base(..., MEMBLOCK_ALLOC_ACCESSIBLE).
The old MEMBLOCK_ALLOC_ANYWHERE changes value from 0 to ~(u64)0 and can still
be used with memblock_alloc_base() to allocate really anywhere.
It is -no-longer- cropped to MEMBLOCK_REAL_LIMIT which disappears.
Note to archs: I'm leaving the default limit to MEMBLOCK_ALLOC_ANYWHERE. I
strongly recommend that you ensure that you set an appropriate limit
during boot in order to guarantee that an memblock_alloc() at any time
results in something that is accessible with a simple __va().
The reason is that a subsequent patch will introduce the ability for
the array to resize itself by reallocating itself. The MEMBLOCK core will
honor the current limit when performing those allocations.
Signed-off-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Diffstat (limited to 'arch/sh/include')
| -rw-r--r-- | arch/sh/include/asm/memblock.h | 2 |
1 files changed, 0 insertions, 2 deletions
diff --git a/arch/sh/include/asm/memblock.h b/arch/sh/include/asm/memblock.h index dfe683b88075..e87063fad2ea 100644 --- a/arch/sh/include/asm/memblock.h +++ b/arch/sh/include/asm/memblock.h @@ -1,6 +1,4 @@ #ifndef __ASM_SH_MEMBLOCK_H #define __ASM_SH_MEMBLOCK_H -#define MEMBLOCK_REAL_LIMIT 0 - #endif /* __ASM_SH_MEMBLOCK_H */ |