Date: Wed, 22 Sep 2010 09:37:12 -0400 From: John Baldwin <jhb@freebsd.org> To: freebsd-current@freebsd.org Cc: Maxim Sobolev <sobomax@freebsd.org>, Jeff Roberson <jeff@freebsd.org>, "current@freebsd.org" <current@freebsd.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: Bumping MAXCPU on amd64? Message-ID: <201009220937.13155.jhb@freebsd.org> In-Reply-To: <4C99DC48.1020208@FreeBSD.org> References: <4C99DC48.1020208@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, September 22, 2010 6:36:56 am Maxim Sobolev wrote: > 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? ? % grep MAXCPU ~/work/freebsd/svn/head/sys/amd64/include/param.h #define MAXCPU 32 #define MAXCPU 1 In fact: % grep MAXCPU ~/work/freebsd/svn/stable/8/sys/amd64/include/param.h #define MAXCPU 32 #define MAXCPU 1 Unfortunately this can't be MFC'd to 7 as it would destroy the ABI for existing klds. -- John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201009220937.13155.jhb>