From owner-freebsd-hackers@FreeBSD.ORG Wed Sep 22 11:16:47 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 1E1471065673 for ; Wed, 22 Sep 2010 11:16:47 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qy0-f175.google.com (mail-qy0-f175.google.com [209.85.216.175]) by mx1.freebsd.org (Postfix) with ESMTP id 7F3C68FC15 for ; Wed, 22 Sep 2010 11:16:46 +0000 (UTC) Received: by qyk31 with SMTP id 31so5686519qyk.13 for ; Wed, 22 Sep 2010 04:16:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type; bh=HOZZgwT9rFmy4LQ068LGIqQdSxBXqRCUYQdWMjPMbqI=; b=w+3NECHb3c2hzk4flj9s0Y9zTQ3UaoEdr/E2aVex5XNAeAIP6q6bmc6oYZoIyhr7EX SL3iEV3FvTvOP2cbqXrjaTq/ewQPOiPJkyykC4bT5SK2ylmzmppN8DEi+M9Mk68GYi2j r9oP3n285LOZZp0KJ4Kv2+FTh5PF+1O0jOeKM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=qDWj2Mo4gEfjSTM1UhkwCFIReE6Bz51cNayTjOWiv/vsfxbu3db6nARDqTkvBUG4YP SZvvinqSL9GkRJONIFNDviyZ0lyZ/A6iEgpIjA9MlMU73RtDSnfo8FIUXeFJ0Gw5oK7I UKR3ycwgcqfFy3VGNCRymSK+AfqMl5LhPDOis= MIME-Version: 1.0 Received: by 10.224.19.200 with SMTP id c8mr13200qab.70.1285154205704; Wed, 22 Sep 2010 04:16:45 -0700 (PDT) Received: by 10.229.50.8 with HTTP; Wed, 22 Sep 2010 04:16:45 -0700 (PDT) In-Reply-To: <4C99DC48.1020208@FreeBSD.org> References: <4C99DC48.1020208@FreeBSD.org> Date: Wed, 22 Sep 2010 15:16:45 +0400 Message-ID: From: pluknet To: Maxim Sobolev Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Hackers , Jeff Roberson , "current@freebsd.org" 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 11:16:47 -0000 2010/9/22 Maxim Sobolev : > Hi, > > Is there any reason to keep MAXCPU at 16 in the default kernel config? There > are quite few servers on the market today that have 24 or even 32 physical > cores. With hyper-threading this can even go as high as 48 or 64 virtual > cpus. People who buy such hardware might get very disappointed finding out > that the FreeBSD is not going to use such hardware to its full potential. > > Does anybody object if I'd bump MAXCPU to 32, which is still low but might > me more reasonable default these days, or at least make it an kernel > configuration option documented in the NOTES? Please correct me, if I'm about smth. different, but isn't it already? /sys/amd64/include/param.h:#define MAXCPU 32 /sys/arm/include/param.h:#define MAXCPU 2 /sys/i386/include/param.h:#define MAXCPU 32 /sys/ia64/include/param.h:#define MAXCPU 32 /sys/mips/include/param.h:#define MAXCPU MAXSMPCPU /sys/powerpc/include/param.h:#define MAXCPU 2 /sys/sparc64/include/param.h:#define MAXCPU 16 /sys/sun4v/include/param.h:#define MAXCPU 32 (almost 2y ago for x86) -- wbr, pluknet