[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20110422093406.FA56.A69D9226@jp.fujitsu.com>
Date: Fri, 22 Apr 2011 09:34:25 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: David Rientjes <rientjes@...gle.com>
Cc: kosaki.motohiro@...fujitsu.com,
James Bottomley <James.Bottomley@...senpartnership.com>,
Pekka Enberg <penberg@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Michal Hocko <mhocko@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>,
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, KOSAKI Motohiro wrote:
>
> > ia64 and mips have CONFIG_ARCH_POPULATES_NODE_MAP and it initialize
> > N_NORMAL_MEMORY automatically if my understand is correct.
> > (plz see free_area_init_nodes)
> >
>
> ia64 doesn't enable CONFIG_HIGHMEM, so it never gets set via this generic
> code; mips also doesn't enable it for all configs even for 32-bit.
>
> So we'll either want to take check_for_regular_memory() out from under
> CONFIG_HIGHMEM and do it for all configs or teach slub to use
> N_HIGH_MEMORY rather than N_NORMAL_MEMORY.
Hey, I already told this thing.
If CONFIG_HIGHMEM=n, N_HIGH_MEMORY and N_NORMAL_MEMORY are share the
same value. then,
node_set_state(nid, N_HIGH_MEMORY) in free_area_init_nodes()
mean set both N_HIGH_MEMORY and N_NORMAL_MEMORY.
--
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