From owner-freebsd-current@FreeBSD.ORG Wed Jul 23 19:31:43 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D484737B401 for ; Wed, 23 Jul 2003 19:31:43 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-67-119-53-152.dsl.lsan03.pacbell.net [67.119.53.152]) by mx1.FreeBSD.org (Postfix) with ESMTP id 32CA543F85 for ; Wed, 23 Jul 2003 19:31:43 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id CD94366D7A; Wed, 23 Jul 2003 19:31:42 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id B52B9C0E; Wed, 23 Jul 2003 19:31:42 -0700 (PDT) Date: Wed, 23 Jul 2003 19:31:42 -0700 From: Kris Kennaway To: "Scott M. Likens" Message-ID: <20030724023142.GB14907@rot13.obsecurity.org> References: <1058994384.89355.1.camel@acheron.livid.de> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="ZfOjI3PrQbgiZnxM" Content-Disposition: inline In-Reply-To: <1058994384.89355.1.camel@acheron.livid.de> User-Agent: Mutt/1.4.1i cc: current@freebsd.org Subject: Re: SMPng status? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 24 Jul 2003 02:31:44 -0000 --ZfOjI3PrQbgiZnxM Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jul 23, 2003 at 02:06:24PM -0700, Scott M. Likens wrote: > Out of curiosity I was wondering what the SMPng status was? >=20 > I have heard it's not fully implemented due to KSE/libthr not fully > implemented. >=20 > I was wondering if this was incorrect information or what? That's not really correct. The SMP threading libraries are one aspect of SMP development work in 5.x, and modulo bugs, optimization, architectural issues and non-i386 platform support they work. The major aspect of SMP development is kernel subsystem locking, which is not yet complete, and will not be for some time. If you're willing to deal with the usual caveats of running -CURRENT, then by all means do so :-) Kris --ZfOjI3PrQbgiZnxM Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/H0UOWry0BWjoQKURAm++AJ9QTxC4u01cdDfZSH3XqXD7gvFNFACgs94G jtbUqrZI/4nyu7PHJyj4gKY= =hWpt -----END PGP SIGNATURE----- --ZfOjI3PrQbgiZnxM--