From owner-freebsd-arch Tue Nov 23 21:54:38 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 0F9A014F83 for ; Tue, 23 Nov 1999 21:54:31 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id GAA24937 for ; Wed, 24 Nov 1999 06:54:09 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id GAA31955 for freebsd-arch@freebsd.org; Wed, 24 Nov 1999 06:54:08 +0100 (MET) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 4643315543; Tue, 23 Nov 1999 21:49:56 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id AAA24224; Wed, 24 Nov 1999 00:49:50 -0500 (EST) Date: Wed, 24 Nov 1999 00:49:49 -0500 (EST) From: Daniel Eischen To: Chuck Robey Cc: Julian Elischer , Nate Williams , freebsd-arch@freebsd.org, jasone@freebsd.org Subject: Re: Threads In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 24 Nov 1999, Chuck Robey wrote: > OK, then let me ask another question: are we at all concerned about maybe > following an already established thread API, or are we going to create our > own? Things like user threads probably could work as then are now (albeit > perhaps with only minor changes in performance) and stuff with runtimes > like Java wouldn't care, but big programs like XFree86 and Netscape, and > specially made daemons trying to do things like mass factoring, > that are going to really want to manipulate real concurrency levels, > they're going to have to be aware of our real underlying API, so making a > unique one will complicate a lot of lives. IMHO, we should stick to the POSIX and perhaps SSv2 standards. We shouldn't be rolling our own non-standard interfaces unless there's a very good reason to. POSIX provides a way to set concurrency levels (pthread_setconcurrency) as well as creating PTHREAD_SCOPE_SYSTEM threads which should compete for processor time with all the other scope system threads in the system. It might be good to see what Java and other systems need from a threads library. Is a fully compliant POSIX threading environment enough? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message