Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 8 Oct 2006 20:11:53 +0800
From:      David Xu <davidxu@freebsd.org>
To:        freebsd-current@freebsd.org
Cc:        Astrodog <astrodog@gmail.com>, current@freebsd.org
Subject:   Re: [PATCH] MAXCPU alterable in kernel config - needs testers
Message-ID:  <200610082011.53649.davidxu@freebsd.org>
In-Reply-To: <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com>
References:  <2fd864e0610080423q7ba6bdeal656a223e662a5d@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200610082011.53649.davidxu>