From owner-freebsd-current@FreeBSD.ORG  Sun Oct  8 12:17:38 2006
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
X-Original-To: freebsd-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 9035516A597
	for <freebsd-current@freebsd.org>; Sun,  8 Oct 2006 12:17:38 +0000 (UTC)
	(envelope-from astrodog@gmail.com)
Received: from wx-out-0506.google.com (wx-out-0506.google.com [66.249.82.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 84056440AA
	for <freebsd-current@freebsd.org>; Sun,  8 Oct 2006 12:16:16 +0000 (GMT)
	(envelope-from astrodog@gmail.com)
Received: by wx-out-0506.google.com with SMTP id i27so1243744wxd
	for <freebsd-current@freebsd.org>; Sun, 08 Oct 2006 05:16:09 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=aQAyRKrVu7MfMv/AFO+uRDadiHZjg9nbh8csLz23ZWn4hXbX0lypabGPgTFuWG1NmeJLUmQtxBcO5Rw9nzyVA7S8cmKkctAglRuKohBHhm+eXOMuW3Rjs4wVvX8Ui7xyG0UAA/QkdpVdvYtJEOBmnWBg/1BZ6o4B0iBvr3CpVt8=
Received: by 10.70.90.18 with SMTP id n18mr9063160wxb;
	Sun, 08 Oct 2006 05:16:09 -0700 (PDT)
Received: by 10.70.118.3 with HTTP; Sun, 8 Oct 2006 05:16:09 -0700 (PDT)
Message-ID: <2fd864e0610080516k6682c101i8d9b83578593fb28@mail.gmail.com>
Date: Sun, 8 Oct 2006 07:16:09 -0500
From: Astrodog <astrodog@gmail.com>
To: "David Xu" <davidxu@freebsd.org>
In-Reply-To: <200610082011.53649.davidxu@freebsd.org>
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>
	<200610082011.53649.davidxu@freebsd.org>
Cc: freebsd-current@freebsd.org, current@freebsd.org
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 12:17:38 -0000

On 10/8/06, David Xu <davidxu@freebsd.org> wrote:
> On Sunday 08 October 2006 19:23, Astrodog 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 think MAXCPU should not be great than 32, since we currently define
> cpumask_t as an integer which now should be changed to a bitmap and
> a group of operations like we did for sigset_t.
>
> David Xu
>

Currently, MAXCPU is 16 on most platforms.