Date: Fri, 22 Oct 2004 19:15:28 +0200
From: Andrea Arcangeli <andrea@novell.com>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, Andrew Morton <akpm@osdl.org>,
       linux-kernel@vger.kernel.org
Subject: Re: ZONE_PADDING wastes 4 bytes of the new cacheline
Message-ID: <20041022171528.GL14325@dualathlon.random>
References: <20041021011714.GQ24619@dualathlon.random> <200410212155.52264.jbarnes@sgi.com> <417880C3.4000807@yahoo.com.au> <200410212249.36535.jbarnes@sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200410212249.36535.jbarnes@sgi.com>
User-Agent: Mutt/1.5.6i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1228
Lines: 22

On Thu, Oct 21, 2004 at 10:49:36PM -0500, Jesse Barnes wrote:
> On Thursday, October 21, 2004 10:38 pm, Nick Piggin wrote:
> > That problem shouldn't exist any more, so your one zone per node (?)
> > NUMA systems, incremental min won't have any effect at all.
> 
> Well, it used to affect us, since as the allocator iterated over nodes, the 
> incremental min would increase, and so by the time we hit the 3rd or so node, 
> we were leaving quite a bit of memory unused.  I just don't want to return to 
> the bad old days.

yes, but all you care about is to turn off the incremental min, you
don't really care about lowmem_reserved, because you don't have floppies
that do ZONE_DMA allocations on ia64, x86-64 would oom-kill tasks just
because insmod floppy.o was running (and this is one of the showstopper
bugs in my queue, I had to disable forced the oom killer to workaroaund
it, apparently the vm can then later on free some page after many loops
despite without swap enabled).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/