From owner-freebsd-current@FreeBSD.ORG  Sun Oct  8 11:24:39 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: current@freebsd.org
Delivered-To: freebsd-current@FreeBSD.ORG
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EED2F16A417
	for <current@freebsd.org>; Sun,  8 Oct 2006 11:24:39 +0000 (UTC)
	(envelope-from astrodog@gmail.com)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.227])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 4FFB743D58
	for <current@freebsd.org>; Sun,  8 Oct 2006 11:24:39 +0000 (GMT)
	(envelope-from astrodog@gmail.com)
Received: by wx-out-0506.google.com with SMTP id i27so1238265wxd
	for <current@freebsd.org>; Sun, 08 Oct 2006 04:24:38 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ZtgTebaaSW4VTSNFapmnyjXA4XmS7YrZryZP1B+PGq9dHa9caCYB8H+pCq9B0SBpfTLvD03mr5QY+GDWILfGDzw6UG5FI9HctNmcvRGusNGPfJp8PUWb3Z7UNNVnndCotSI+iqyPffCieDnhFB3FSa/Vl+ptiOlFoCH2na5soc4=
Received: by 10.70.77.2 with SMTP id z2mr9029267wxa;
	Sun, 08 Oct 2006 04:24:38 -0700 (PDT)
Received: by 10.70.118.3 with HTTP; Sun, 8 Oct 2006 04:24:38 -0700 (PDT)
Message-ID: <2fd864e0610080424y5bad6c83w9be90d1fca19c7d4@mail.gmail.com>
Date: Sun, 8 Oct 2006 06:24:38 -0500
From: Astrodog <astrodog@gmail.com>
To: current@freebsd.org
In-Reply-To: <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com>
Cc: 
Subject: Re: [PATCH] MAXCPU alterable in kernel config - needs testers
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Oct 2006 11:24:40 -0000

On 10/8/06, Astrodog <astrodog@gmail.com> wrote:
> With the quad core processors coming out soon, this is going to become
> more of an issue.. (Sun T1/2000s aside). This is basically the same
> patch from a few months ago, with updated offsets.
>
> If you don't define MAXCPU in the kernel config, it reverts to old
> behavior. It has no logic to keep you from shooting yourself in the
> foot though.. you can define options SMP and options MAXCPU 128 on
> arm.
>
> --- Harrison Grundy
>

I guess including a link to the patch might help...

http://72.232.65.146/~astrodog/NEWMAXCPU.diff