[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1104211411540.20201@chino.kir.corp.google.com>
Date: Thu, 21 Apr 2011 14:19:45 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: Christoph Lameter <cl@...ux.com>,
James Bottomley <James.Bottomley@...senpartnership.com>,
Andrew Morton <akpm@...ux-foundation.org>
cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Pekka Enberg <penberg@...nel.org>,
Michal Hocko <mhocko@...e.cz>, Hugh Dickins <hughd@...gle.com>,
linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>,
linux-parisc@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH v3] mm: make expand_downwards symmetrical to
expand_upwards
On Thu, 21 Apr 2011, Christoph Lameter wrote:
> In 32 bit configurations some architectures (like x86) provide nodes
> that have only high memory. Slab allocators only handle normal memory.
> SLAB operates in a kind of degraded mode in that case by falling back for
> each allocation to the nodes that have normal memory.
>
Let's do this:
- parisc: James has already queued "parisc: set memory ranges in
N_NORMAL_MEMORY when onlined" for 2.6.39, so all he needs now is
to merge a hybrid of the Kconfig changes requiring CONFIG_NUMA for
CONFIG_DISCONTIGMEM from KOSAKI-san and myself which also fix the
compile issues,
- generic code: we pull check_for_regular_memory() out from under
CONFIG_HIGHMEM so that N_NORMAL_MEMORY gets set appropriately for
all callers of free_area_init_nodes() from paging_init(); this fixes
ia64 and mips,
- alpha, m32r, m68k: push the changes to those individual architectures
that I proposed earlier that set N_NORMAL_MEMORY for DISCONTINGMEM
when memory regions have memory; KOSAKI-san says a couple of these
architectures may be orphaned so hopefully Andrew can pick them up
in -mm.
I'll reply to this email with the parisc Kconfig changes for James, the
generic change to check_for_regular_memory() for Andrew, and the
arch-specific changes to the appropriate maintainers and email lists (but
may need to go through -mm if they aren't picked up).
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists