From owner-freebsd-hackers Wed Dec 11 11:06:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA29391 for hackers-outgoing; Wed, 11 Dec 1996 11:06:29 -0800 (PST) Received: from ki1.chemie.fu-berlin.de (ki1.Chemie.FU-Berlin.DE [160.45.24.21]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA29365 for ; Wed, 11 Dec 1996 11:06:16 -0800 (PST) Received: by ki1.chemie.fu-berlin.de (Smail3.1.28.1) from mail.hanse.de (193.174.9.9) with smtp id ; Wed, 11 Dec 96 20:06 MET Received: from wavehh.UUCP by mail.hanse.de with UUCP for freebsd-hackers@freebsd.org id ; Wed, 11 Dec 96 20:06 MET Received: by wavehh.hanse.de (4.1/SMI-4.1) id AA17058; Wed, 11 Dec 96 19:57:41 +0100 From: cracauer@wavehh.hanse.de (Martin Cracauer) Message-Id: <9612111857.AA17058@wavehh.hanse.de> Subject: FDW: pthreads based on kernel managed threads for FreeBSD 2.1 almost ready To: freebsd-hackers@freebsd.org Date: Wed, 11 Dec 1996 19:57:40 +0100 (MET) Cc: doug@qnx.com X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [ I forwarded this message to the freebsd-hackers mailing list. ] This guy asks for help in finishing a kernel-thread thread solution. Would be intersting to see at least the performance penality over a userlevel package or a mixed model like the DEC work discussed here some days ago. I think you can get many useful locking items from the linuxthreads package, which is a pthread implementation on top of Linux' clone() call (somewhat equivalent to rfork()). Get it from alpha.gnu.prep.ai.mit.edu. It is GPLed, of course. Martin >From: doug@qnx.com (Doug Santry) >Newsgroups: comp.unix.bsd.freebsd.misc >Subject: pthreads based on kernel managed threads for FreeBSD 2.1 almost ready >Date: 10 Dec 1996 10:24:14 -0500 >Organization: QNX Software Systems >Message-ID: <58jvau$9tt@qnx.com> Hi y'all. I am currently working on a pthreads interface to my kernel managed threads for FreeBSD 2.1, the first release won't be complete, I plan to support : pthread_create, pthread_join, pthread_kill, pthread_sigmask, pthread_exit pthread_self and pthread_detached. In addition to the above there will also be pthread_mutex_init and the lock, unlock trylock and destroy functions. The code is all written but still buggy so I am hanging onto it a bit longer, but when I send it out, you can see it isn't complete by any means. I need your help! Is anybody out there interested in writing the condvar stuff and some other bits? I simply haven't got the time do it all in a useful timeframe... DJS