- Subject: Re: [PATCH v3] mm: make expand_downwards symmetrical to expand_upwards
- From: Matthew Wilcox <matthew@xxxxxx>
- Date: Wed, 20 Apr 2011 05:20:20 -0600
- Cc: KOSAKI Motohiro <kosaki.motohiro@xxxxxxxxxxxxxx>, Christoph Lameter <cl@xxxxxxxxx>, James Bottomley <James.Bottomley@xxxxxxxxxxxxxxxxxxxxx>, Michal Hocko <mhocko@xxxxxxx>, Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>, Hugh Dickins <hughd@xxxxxxxxxx>, linux-mm@xxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>, linux-parisc@xxxxxxxxxxxxxxx, David Rientjes <rientjes@xxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, x86 maintainers <x86@xxxxxxxxxx>
- In-reply-to: <BANLkTimfpY3gq8oY6bPDajBW7JN6Hp+A0A@xxxxxxxxxxxxxx>
- References: <20110420102314.4604.A69D9226@xxxxxxxxxxxxxx> <BANLkTi=mxWwLPEnB+rGg29b06xNUD0XvsA@xxxxxxxxxxxxxx> <20110420161615.462D.A69D9226@xxxxxxxxxxxxxx> <BANLkTimfpY3gq8oY6bPDajBW7JN6Hp+A0A@xxxxxxxxxxxxxx>
- User-agent: Mutt/1.5.18 (2008-05-17)
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.
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?
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.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
To unsubscribe from this list: send the line "unsubscribe linux-parisc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Linux USB Devel]
[Video for Linux]
[Linux Audio Users]
[Photo]
[Yosemite News]
[Yosemite Photos]
[Free Online Dating]
[Linux Kernel]
[Linux SCSI]
[XFree86]