From owner-freebsd-current Fri Dec 26 22:53:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA08650 for current-outgoing; Fri, 26 Dec 1997 22:53:44 -0800 (PST) (envelope-from owner-freebsd-current) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA08374; Fri, 26 Dec 1997 22:48:19 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id WAA00376; Fri, 26 Dec 1997 22:48:07 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199712270648.WAA00376@rah.star-gate.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: John Birrell cc: hsu@freebsd.org (Jeffrey Hsu), freebsd-current@freebsd.org Subject: Re: kernel threads api? In-reply-to: Your message of "Sat, 27 Dec 1997 17:19:00 +1100." <199712270619.RAA10165@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 26 Dec 1997 22:48:07 -0800 From: Amancio Hasty Sender: owner-freebsd-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What is libpthread ? 8) Tnks, Amancio > Jeffrey Hsu wrote: > > Life could be simpler if we just > > made libc re-entrant and not distinguish libc from libc_r or libpthread. > > With the work that John Dyson has done (is doing 8-) on kernel threads, > libc_r can die and be replaced by libpthread + libc. This is made possible > because any thread can block on a syscall and the kernel will schedule > another thread. Without kernel threads, blocking syscalls are problematic > to libc_r, as you know 8-). Of course there is still a lot of work > required to make libc re-entrant. > > Regards, > > -- > John Birrell - jb@cimlogic.com.au; jb@netbsd.org; jb@freebsd.org > CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137