Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752568AbWAFVBA (ORCPT ); Fri, 6 Jan 2006 16:01:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752567AbWAFVBA (ORCPT ); Fri, 6 Jan 2006 16:01:00 -0500 Received: from mx1.redhat.com ([66.187.233.31]:17128 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1752565AbWAFVA7 (ORCPT ); Fri, 6 Jan 2006 16:00:59 -0500 Date: Fri, 6 Jan 2006 16:00:24 -0500 From: Dave Jones To: Christoph Lameter Cc: "Randy.Dunlap" , Matthew Wilcox , "Luck, Tony" , 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: <20060106210024.GK4595@redhat.com> Mail-Followup-To: Dave Jones , Christoph Lameter , "Randy.Dunlap" , Matthew Wilcox , "Luck, Tony" , 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 References: <20060106174957.GF19769@parisc-linux.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1365 Lines: 31 On Fri, Jan 06, 2006 at 10:37:33AM -0800, Christoph Lameter wrote: > On Fri, 6 Jan 2006, Randy.Dunlap wrote: > > > > The dicey thing in all of this is that the generic kernels will be used > > > for the certification of applications. If the cpu limit is too low then > > > applications will simply not be certified for these high processor counts. > > > One may encounter problems if the app is then run with a higher processor > > > count. > > > > Do you equate a 'defconfig' kernel with a generic kernel? > > > > I would expect certs to be done on vendor kernels, and as > > Arjan has suggested, they will have their own configs, > > not defconfig. > > Vendors look for the upstream defaults and orient themselves on the > defconfig. It is best to have as much common code and configurations as > possible. As someone who builds vendor kernels, I can say this isn't true (from my experience at least). When a new config option appears, I look at the Kconfig, and make a decision. I *never* even look at the defconfig, as a lot of the time, they are either out of date, or irrelevant. Dave - 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/