Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262939AbVDAWtY (ORCPT ); Fri, 1 Apr 2005 17:49:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262945AbVDAWtY (ORCPT ); Fri, 1 Apr 2005 17:49:24 -0500 Received: from fire.osdl.org ([65.172.181.4]:8085 "EHLO smtp.osdl.org") by vger.kernel.org with ESMTP id S262939AbVDAWtS (ORCPT ); Fri, 1 Apr 2005 17:49:18 -0500 Date: Fri, 1 Apr 2005 14:51:12 -0800 (PST) From: Linus Torvalds To: "Chen, Kenneth W" cc: "'Ingo Molnar'" , Paul Jackson , Nick Piggin , akpm@osdl.org, linux-kernel@vger.kernel.org Subject: RE: Industry db benchmark result on recent 2.6 kernels In-Reply-To: <200504012232.j31MWTg03706@unix-os.sc.intel.com> Message-ID: References: <200504012232.j31MWTg03706@unix-os.sc.intel.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1199 Lines: 30 On Fri, 1 Apr 2005, Chen, Kenneth W wrote: > > Paul, you definitely want to check this out on your large numa box. I booted > a kernel with this patch on a 32-way numa box and it took a long .... time > to produce the cost matrix. Is there anything fundamentally wrong with the notion of just initializing the cost matrix to something that isn't completely wrong at bootup, and just lettign user space fill it in? Then you couple that with a program that can do so automatically (ie move the in-kernel heuristics into user-land), and something that can re-load it on demand. Voila - you have something potentially expensive that you run once, and then you have a matrix that can be edited by the sysadmin later and just re-loaded at each boot.. That sounds pretty optimal, especially in the sense that it allows the sysadmin to tweak things depending on the use of the box is he really wants to. Hmm? Or am I just totally on crack? Linus - 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/