From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2992704AbXCBWvT (ORCPT ); Fri, 2 Mar 2007 17:51:19 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S2992705AbXCBWvS (ORCPT ); Fri, 2 Mar 2007 17:51:18 -0500 Received: from dvhart.com ([64.146.134.43]:39350 "EHLO dvhart.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2992704AbXCBWvS (ORCPT ); Fri, 2 Mar 2007 17:51:18 -0500 Message-ID: <45E8AA64.3050506@mbligh.org> Date: Fri, 02 Mar 2007 14:51:16 -0800 From: Martin Bligh User-Agent: Thunderbird 1.5.0.8 (X11/20061117) MIME-Version: 1.0 To: Rik van Riel Cc: Andrew Morton , Bill Irwin , Christoph Lameter , Mel Gorman , npiggin@suse.de, mingo@elte.hu, jschopp@austin.ibm.com, arjan@infradead.org, torvalds@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: The performance and behaviour of the anti-fragmentation related patches References: <20070301101249.GA29351@skynet.ie> <20070301160915.6da876c5.akpm@linux-foundation.org> <45E842F6.5010105@redhat.com> <20070302085838.bcf9099e.akpm@linux-foundation.org> <20070302093501.34c6ef2a.akpm@linux-foundation.org> <45E8624E.2080001@redhat.com> <20070302100619.cec06d6a.akpm@linux-foundation.org> <45E86BA0.50508@redhat.com> <20070302211207.GJ10643@holomorphy.com> <45E894D7.2040309@redhat.com> <20070302135243.ada51084.akpm@linux-foundation.org> <45E89F1E.8020803@redhat.com> <20070302142256.0127f5ac.akpm@linux-foundation.org> <45E8A677.7000205@redhat.com> In-Reply-To: <45E8A677.7000205@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org >> None of this is going anywhere, is is it? > > I will test my changes before I send them to you, but I cannot > promise you that you'll have the computers or software needed > to reproduce the problems. I doubt I'll have full time access > to such systems myself, either. > > 32GB is pretty much the minimum size to reproduce some of these > problems. Some workloads may need larger systems to easily trigger > them. We can find a 32GB system here pretty easily to test things on if need be. Setting up large commercial databases is much harder. I don't have such a machine in the public set of machines we're going to push to test.kernel.org from at the moment, but will see if I can arrange it in the future if it's important. M.