[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BANLkTim+m-v-4k17HUSOYSbmNFDtJTgD6g@mail.gmail.com>
Date: Wed, 20 Apr 2011 14:28:26 +0300
From: Pekka Enberg <penberg@...nel.org>
To: Matthew Wilcox <matthew@....cx>
Cc: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
Christoph Lameter <cl@...ux.com>,
James Bottomley <James.Bottomley@...senpartnership.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, David Rientjes <rientjes@...gle.com>,
Ingo Molnar <mingo@...e.hu>, x86 maintainers <x86@...nel.org>
Subject: Re: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards
Hi Matthew,
On Wed, Apr 20, 2011 at 10:34:23AM +0300, Pekka Enberg wrote:
>> That part makes me think the best option is to make parisc do
>> CONFIG_NUMA as well regardless of the historical intent was.
On Wed, Apr 20, 2011 at 2:20 PM, Matthew Wilcox <matthew@....cx> wrote:
> But it's not just parisc. It's six other architectures as well, some
> of which aren't even SMP. Does !SMP && NUMA make any kind of sense?
IIRC, we actually fixed SLAB or SLUB to work on such configs in the past.
On Wed, Apr 20, 2011 at 2:20 PM, Matthew Wilcox <matthew@....cx> wrote:
> I think really, this is just a giant horrible misunderstanding on the part
> of the MM people. There's no reason why an ARM chip with 16MB of memory
> at 0 and 16MB of memory at 1GB should be saddled with all the NUMA gunk.
Right. My point was simply that since x86 doesn't support DISCONTIGMEM
without NUMA, the misunderstanding is likely very wide-spread.
Pekka
--
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