Files
linux/arch/sh/include/asm
Benjamin Herrenschmidt e63075a3c9 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>
2010-08-05 12:56:07 +10:00
..
2010-03-09 11:57:17 +09:00
2010-01-27 22:36:25 +09:00
2010-03-29 12:04:19 +09:00
2009-05-29 08:40:02 -07:00
2009-11-30 12:02:53 +09:00
2009-10-14 16:42:28 +09:00
2010-05-11 11:48:47 +09:00
2010-06-02 16:31:42 +09:00
2010-04-26 19:08:55 +09:00
2009-05-09 16:02:08 +09:00
2010-03-10 16:29:48 +09:00
2010-05-11 13:32:19 +09:00
2010-01-13 19:11:14 +09:00
2010-01-20 16:42:52 +09:00
2009-09-11 13:19:16 +09:00
2009-04-27 17:34:39 +09:00
2009-11-09 10:47:40 +09:00
2008-08-02 04:39:32 +09:00
2009-08-14 01:58:43 +09:00
2010-05-11 13:32:19 +09:00
2009-06-14 23:25:57 +09:00
2010-04-26 19:08:55 +09:00
2010-04-26 19:08:55 +09:00
2008-09-08 10:35:04 +09:00
2010-03-12 15:52:32 -08:00
2010-02-12 15:40:00 +09:00
2008-08-04 12:51:06 +09:00
2010-03-12 15:52:32 -08:00
2010-03-12 15:52:32 -08:00