[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.64.0703012031410.14299@schroedinger.engr.sgi.com>
Date: Thu, 1 Mar 2007 20:33:04 -0800 (PST)
From: Christoph Lameter <clameter@...r.sgi.com>
To: Andrew Morton <akpm@...ux-foundation.org>
cc: Nick Piggin <npiggin@...e.de>, Mel Gorman <mel@...net.ie>,
mingo@...e.hu, jschopp@...tin.ibm.com, arjan@...radead.org,
torvalds@...ux-foundation.org, mbligh@...igh.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: The performance and behaviour of the anti-fragmentation related
patches
On Thu, 1 Mar 2007, Andrew Morton wrote:
> Sorry, but this is crap. zones and nodes are distinct, physical concepts
> and you're kidding yourself if you think you can somehow fudge things to make
> one of them just go away.
>
> Think: ZONE_DMA32 on an Opteron machine. I don't think there is a sane way
> in which we can fudge away the distinction between
> bus-addresses-which-have-the-32-upper-bits-zero and
> memory-which-is-local-to-each-socket.
Of course you can. Add a virtual DMA and DMA32 zone/node and extract the
relevant memory from the base zone/node.
-
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