From owner-freebsd-questions Mon Jan 17 7:43:54 2000 Delivered-To: freebsd-questions@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id 863E914DF0 for ; Mon, 17 Jan 2000 07:43:51 -0800 (PST) (envelope-from jcm@dogma.freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) id 12AEJm-000GCy-00; Mon, 17 Jan 2000 15:43:46 +0000 Received: from localhost (jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) with ESMTP id PAA13048; Mon, 17 Jan 2000 15:43:45 GMT (envelope-from jcm@dogma.freebsd-uk.eu.org) Date: Mon, 17 Jan 2000 15:43:45 +0000 (GMT) From: Jonathon McKitrick To: Glen Driban Cc: freebsd-questions@freebsd.org Subject: Re: kernel threads In-Reply-To: <38833318.657CF494@wgate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Glen Driban wrote: >Any support in any of the 3.x releases for kernel threads? I can only >find reference to pthreads. I've searched the freeBSD.org site, looked >at the FAQ's and looked at the 3.x release notes. If no support for >kernel threads is it planned for the future and in what release might we >expect to see it. There are no kernel threads at the moment, but FreeBSD still has fantastic performance. Apparently they are now discussing what kind of architecture they want to use to implement kernel threads in the future. It probably will be a while away, however. Since 4.0 is due out soon, maybe they will start on kernel threads in -current after this release, and they will spend a while hammering out the details and bugs. > >-- >Glenn Driban >Senior Software Engineer >Worldgate Communications, Inc. > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > -=> jm <=- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message