(on -hackers only, as this post is beyond the -smp charter)
> > 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.
Ah, okay. Thanks.
I use this approach, too, but not for threads; I relegate this type of
architecture to state machines. I guess that cramming multiple threads
into a single PID would be considered a state machine of sorts...
Sounds like I need to just ignore libc_r and stick to syscalls and what
I've been doing. I must note, however, that the "uthreads" source
directory for libc_r provides a handy checklist of functions that might
need a bit of TLC. :-)
Thanks again,
Eddy
---------------------------------------------------------------------------
Brotsman & Dreger, Inc.
EverQuick Internet Division
Phone: +1 (316) 794-8922 Wichita/(Inter)national
Phone: +1 (785) 865-5885 Lawrence
---------------------------------------------------------------------------
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
