[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.1205091252450.11225@router.home>
Date: Wed, 9 May 2012 12:54:37 -0500 (CDT)
From: Christoph Lameter <cl@...ux.com>
To: Tejun Heo <tj@...nel.org>
cc: Sam Ravnborg <sam@...nborg.org>,
Johannes Weiner <hannes@...xchg.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Gavin Shan <shangw@...ux.vnet.ibm.com>,
David Miller <davem@...emloft.net>,
Yinghai Lu <yinghai@...nel.org>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>
Subject: Re: [patch 00/10] (no)bootmem bits for 3.5
On Wed, 9 May 2012, Tejun Heo wrote:
> Indeed, preferring node 0 for bootmem allocation on x86_32 got lost
> across the nobootmem changes. I followed the git history and
> preferring NODE_DATA(0) goes back to the initial git branch creation
> time (2.6.12) and I couldn't find any explanation, and nobody
> complained about the changed behavior. hpa, do you know why the code
> to prefer node 0 for bootmem allocations was added in the first place?
> Maybe we can just remove it?
On some early 32 bit NUMA platforms only node 0 had ZONE_NORMAL memory.
There is just no other ZONE_NORMAL memory available on other nodes on that
hardware. But that is ancient history.
Wondering if 32 bit numa machines still exist. If so how do they partition
memory below 1G?
--
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