Date: Fri, 26 Dec 1997 22:48:07 -0800 From: Amancio Hasty <hasty@rah.star-gate.com> To: John Birrell <jb@freebsd1.cimlogic.com.au> Cc: hsu@freebsd.org (Jeffrey Hsu), freebsd-current@freebsd.org Subject: Re: kernel threads api? Message-ID: <199712270648.WAA00376@rah.star-gate.com> In-Reply-To: Your message of "Sat, 27 Dec 1997 17:19:00 %2B1100." <199712270619.RAA10165@cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712270648.WAA00376>