Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932771AbWAFR0X (ORCPT ); Fri, 6 Jan 2006 12:26:23 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S964784AbWAFR0V (ORCPT ); Fri, 6 Jan 2006 12:26:21 -0500 Received: from palinux.external.hp.com ([192.25.206.14]:56792 "EHLO palinux.hppa") by vger.kernel.org with ESMTP id S932758AbWAFR0Q (ORCPT ); Fri, 6 Jan 2006 12:26:16 -0500 Date: Fri, 6 Jan 2006 10:26:15 -0700 From: Matthew Wilcox To: "Luck, Tony" Cc: Arjan van de Ven , hawkes@sgi.com, Tony Luck , Andrew Morton , linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org, Jack Steiner , Dan Higgins , John Hesterberg , Greg Edwards Subject: Re: [PATCH] ia64: change defconfig to NR_CPUS==1024 Message-ID: <20060106172615.GE19769@parisc-linux.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.9i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 758 Lines: 14 On Fri, Jan 06, 2006 at 09:19:28AM -0800, Luck, Tony wrote: > Would it be impossibly hard to make the >64 cpus case (when the code > switches from a single word to an array) be dependent on a boot-time > variable? If we could, then the defconfig could just say 128, and > users of monster machines would just boot with "maxcpus=4096" to increase > the size of the bitmask arrays. Why can't we keep the default below 64? Surely the 0.1% of the market which needs more than 64 cpus can recompile their kernel ... - 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/