Date: Mon, 1 Nov 1999 18:57:05 +1100 From: John Birrell <jb@cimlogic.com.au> To: Julian Elischer <julian@whistle.com> Cc: freebsd-arch@freebsd.org Subject: Re: Threads goals version III Message-ID: <19991101185705.A55580@freebsd1.cimlogic.com.au> In-Reply-To: <Pine.BSF.4.05.9910311908080.8816-100000@home.elischer.org>; from Julian Elischer on Sun, Oct 31, 1999 at 07:09:04PM -0800 References: <Pine.BSF.4.05.9910311908080.8816-100000@home.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[ Grrr, I'm obviously in a different timezone from this discussion. ] On Sun, Oct 31, 1999 at 07:09:04PM -0800, Julian Elischer wrote: > 10/ Quick access to curthread and thread specific data. 10a/ Quick access to mutex state. One of the things that affects the performance of a threaded application is the time that is consumed testing the state of a mutex. Without trying to push this discussion into the "how it should be done phase", just consider sharing mutex state between user- and kernel- space. We will need a VM wizard at some point. 8-) > ---- possible userland implementation goals----- > > 1/ A libpthread that can be linked with libc. > > 2/ Libc needs to change so that library functions and system calls > used internal to the library do not use the externally visible > cancellable equivalents. A big re-write of libc is required. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ john.birrell@cai.com john.birrell@opendirectory.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19991101185705.A55580>