From owner-freebsd-current Wed Apr 15 23:07:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA19992 for freebsd-current-outgoing; Wed, 15 Apr 1998 23:07:14 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlogic.com.au [203.36.2.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA19950 for ; Wed, 15 Apr 1998 23:07:01 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.5/8.8.7) id QAA02962; Thu, 16 Apr 1998 16:05:45 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199804160605.QAA02962@cimlogic.com.au> Subject: Re: Status of native threads on CURRENT / Support for mySQL In-Reply-To: from Michael Hancock at "Apr 16, 98 02:50:44 pm" To: michaelh@cet.co.jp (Michael Hancock) Date: Thu, 16 Apr 1998 16:05:44 +1000 (EST) Cc: freebsd@atipa.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Hancock wrote: > If you're looking for stability in a production environment stay away from > current for a little while as there is a lot of new activity including > vm/vfs/cam/softupdates/elf/posix/microtime/alpha/sparc that's going to > take a little while to settle even with careful planning and testing. > > I think thread work is suspended until some dependent underlying vm > projects are completed. The _kernel_ thread work is limping along. It hasn't quite come to a halt. 8-) The code in libc_r passes all my local tests that include some rather big applications with performance comparisons of the same code running under OSF/1, including some X based. There have been changes recently to allow for kernel threading as an alternative, but these are insignificant. The elf, posix (realtime), alpha and sparc things won't destabilise the system, IMO. It looks like the microtime changes have been pretty much digested too. As always, -current in a production environment is a risk, but the system looks stable at present. YMMV. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message