Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Sep 2010 22:42:26 +0100 (BST)
From:      Robert Watson <rwatson@FreeBSD.org>
To:        John Baldwin <jhb@freebsd.org>
Cc:        "sbruno@freebsd.org" <sbruno@freebsd.org>, freebsd-current@freebsd.org, Sean Bruno <seanbru@yahoo-inc.com>, "current@freebsd.org" <current@freebsd.org>
Subject:   Re: MAXCPU preparations
Message-ID:  <alpine.BSF.2.00.1009272240340.69239@fledge.watson.org>
In-Reply-To: <201009271738.19497.jhb@freebsd.org>
References:  <1285601161.7245.7.camel@home-yahoo> <1285604516.7245.16.camel@home-yahoo> <alpine.BSF.2.00.1009272210040.69239@fledge.watson.org> <201009271738.19497.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Mon, 27 Sep 2010, John Baldwin wrote:

> Also, I think we should either fix MAXCPU to export the SMP value to 
> userland, or hide it from userland completely.  Exporting the UP value is 
> Just Wrong (tm).

Well, it's useful in the sense that it tells you what the maximum number of 
CPUs a kernel can support is, which is helpful, especially if you're futzing 
with MAXCPU as a kernel option :-).

But, more generally, many things that use MAXCPU should probably use either 
mp_maxid or DPCPU.  Not everything, but most things.

Robert



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