Date: Thu, 28 Jun 2001 23:33:56 -0500 From: Chris Costello <chris@calldei.com> To: "E.B. Dreger" <eddy+public+spam@noc.everquick.net> Cc: freebsd-smp@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: libc_r locking... why? Message-ID: <20010628233355.F55395@holly.calldei.com> In-Reply-To: <Pine.LNX.4.20.0106290356480.3220-100000@www.everquick.net>; from eddy%2Bpublic%2Bspam@noc.everquick.net on Fri, Jun 29, 2001 at 04:20:51AM %2B0000 References: <20010628212856.E55395@holly.calldei.com> <Pine.LNX.4.20.0106290356480.3220-100000@www.everquick.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, June 29, 2001, E.B. Dreger wrote: > Am I correct that libc_r does _not_ use multiple processes to create > threads? Grepping for "fork" in *.c files under /usr/src/lib/libc_r leads > me to believe that this is so... That's correct. It's implemented using setjmp/longjmp, and storing stack pointers and the like in thread-specific data structures. -- +-------------------+--------------------------------+ | Chris Costello | A bug in the code is worth two | | chris@calldei.com | in the documentation. | +-------------------+--------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010628233355.F55395>