Re: [patch 10/10] mm: remove sparsemem allocation details from thebootmem allocator

From: Andrew Morton
Date: Thu May 10 2012 - 17:44:36 EST


On Mon, 7 May 2012 13:37:52 +0200
Johannes Weiner <hannes@xxxxxxxxxxx> wrote:

> alloc_bootmem_section() derives allocation area constraints from the
> specified sparsemem section. This is a bit specific for a generic
> memory allocator like bootmem, though, so move it over to sparsemem.
>
> As __alloc_bootmem_node_nopanic() already retries failed allocations
> with relaxed area constraints, the fallback code in sparsemem.c can be
> removed and the code becomes a bit more compact overall.
>
> ...
>
> @@ -332,9 +334,9 @@ static void __init check_usemap_section_nr(int nid, unsigned long *usemap)
> #else
> static unsigned long * __init
> sparse_early_usemaps_alloc_pgdat_section(struct pglist_data *pgdat,
> - unsigned long count)
> + unsigned long size)
> {
> - return NULL;
> + return alloc_bootmem_node_nopanic(pgdat, size)

You've been bad. Your penance is to runtime test this code with
CONFIG_MEMORY_HOTREMOVE=n!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/