From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 22 21:06:19 2010 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 343581065670 for ; Wed, 22 Sep 2010 21:06:19 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from cyrus.watson.org (cyrus.watson.org [65.122.17.42]) by mx1.freebsd.org (Postfix) with ESMTP id 076B78FC17 for ; Wed, 22 Sep 2010 21:06:19 +0000 (UTC) Received: from bigwig.baldwin.cx (66.111.2.69.static.nyinternet.net [66.111.2.69]) by cyrus.watson.org (Postfix) with ESMTPSA id 99C8846B0C; Wed, 22 Sep 2010 17:06:18 -0400 (EDT) Received: from jhbbsd.localnet (smtp.hudson-trading.com [209.249.190.9]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id C0C558A03C; Wed, 22 Sep 2010 17:06:17 -0400 (EDT) From: John Baldwin To: freebsd-hackers@freebsd.org Date: Wed, 22 Sep 2010 17:04:56 -0400 User-Agent: KMail/1.13.5 (FreeBSD/7.3-CBSD-20100819; KDE/4.4.5; amd64; ; ) References: <4C99DC48.1020208@FreeBSD.org> <201009220937.13155.jhb@freebsd.org> <4C9A380E.7070807@gmail.com> In-Reply-To: <4C9A380E.7070807@gmail.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="koi8-u" Content-Transfer-Encoding: 7bit Message-Id: <201009221704.56514.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0.1 (bigwig.baldwin.cx); Wed, 22 Sep 2010 17:06:17 -0400 (EDT) X-Virus-Scanned: clamav-milter 0.95.1 at bigwig.baldwin.cx X-Virus-Status: Clean X-Spam-Status: No, score=-2.6 required=4.2 tests=AWL,BAYES_00 autolearn=ham version=3.2.5 X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on bigwig.baldwin.cx Cc: Curtis Penner Subject: Re: Bumping MAXCPU on amd64? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Sep 2010 21:06:19 -0000 On Wednesday, September 22, 2010 1:08:30 pm Curtis Penner wrote: > MAXCPU at 32 has been good in the 32bit days. Soon there will be (if > not already) systems that will have 16cores/socket or more, and > motherboards that have 4 sockets or more. Combining this with > hyper-threading, you have gone significantly beyond the limits of > feasible server. My point was in response to Maxim's mail about bumping it from 16. Going higher than 32 is a bigger project (but in progress-ish) as it involves transitioning away from a simple int to hold CPU ID bitmasks (cpumask_t) and using cpuset_t instead. -- John Baldwin