From owner-freebsd-current@FreeBSD.ORG Sun Oct 8 12:11:56 2006 Return-Path: X-Original-To: current@freebsd.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from localhost.my.domain (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 11D8F16A47B; Sun, 8 Oct 2006 12:11:56 +0000 (UTC) (envelope-from davidxu@freebsd.org) From: David Xu To: freebsd-current@freebsd.org Date: Sun, 8 Oct 2006 20:11:53 +0800 User-Agent: KMail/1.8.2 References: <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com> In-Reply-To: <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200610082011.53649.davidxu@freebsd.org> Cc: Astrodog , 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Oct 2006 12:11:57 -0000 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