From owner-freebsd-current Wed Oct 21 06:34:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA17365 for freebsd-current-outgoing; Wed, 21 Oct 1998 06:34:10 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opi.flirtbox.ch ([62.48.0.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA17347 for ; Wed, 21 Oct 1998 06:34:07 -0700 (PDT) (envelope-from oppermann@pipeline.ch) Received: (qmail 6125 invoked from network); 21 Oct 1998 13:05:49 -0000 Received: from unknown (HELO pipeline.ch) (195.134.140.4) by opi.flirtbox.ch with SMTP; 21 Oct 1998 13:05:49 -0000 Message-ID: <362DDC74.B04C3057@pipeline.ch> Date: Wed, 21 Oct 1998 15:07:00 +0200 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: Alfred Perlstein CC: HighWind Software Information , current@FreeBSD.ORG Subject: Re: Another Serious libc_r problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: -snip- > As a side note, has anyone thought of hybrid kernel+userland threads? > Basically a userland scheduler with kernel hooks for mutexes and > distributing signals. At startup or on the first pthread_create() the > pthreads library would sysctl out the number of processors in the > system and prefork kernel threads for each. The kernel threads would only > be active on SMP machines, otherwise there really is no point. Does > anyone have any papers/webpages about an algorithm like that? http://www.freebsd.org/~terry (I think so...) -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message