[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1104211431500.20201@chino.kir.corp.google.com>
Date: Thu, 21 Apr 2011 14:34:00 -0700 (PDT)
From: David Rientjes <rientjes@...gle.com>
To: James Bottomley <James.Bottomley@...senpartnership.com>
cc: Christoph Lameter <cl@...ux.com>,
Andrew Morton <akpm@...ux-foundation.org>,
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, James Bottomley wrote:
> > - 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,
>
> Not quite: if we go this route, we need to sort out our CPU scheduling
> problem as well ... as I said, I don't think we've got all the necessary
> numa machinery in place yet.
>
Ok, it seems like there're two options for this release cycle:
(1) merge the patch that enables CONFIG_NUMA for DISCONTIGMEM but only
do so if CONFIG_SLUB is enabled to avoid the build error, or
(2) disallow CONFIG_SLUB for parisc with DISCONTIGMEM.
--
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