Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!seismo!sundc!pitstop!sun!amdcad!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!encore!multimax!boykin
From: boykin@multimax.Encore.COM (Joe Boykin)
Newsgroups: comp.sys.misc
Subject: Re: NeXT & "threads"
Message-ID: <4034@encore.UUCP>
Date: 28 Oct 88 19:39:20 GMT
Article-I.D.: encore.4034
References: <10736@reed.UUCP> <363@thor.wright.EDU> <3022@haven.umd.edu> <2821@ima.ima.isc.com> <19648@apple.Apple.COM>
Sender: news@encore.UUCP
Reply-To: boykin@multimax.UUCP (Joe Boykin)
Organization: Encore Computer Corp, Marlboro, MA
Lines: 20

>BTW, in Mach are threads a kernel feature like fork(), or just a
>library call? 

Threads are implemented within the MACH kernel directly.  When
you do a unix fork() you really get a task with a single thread.
That thread can then do a "thread_create()" to create more
threads.  There is a little bit of work to set up the new
thread, such as suppling a new stack, initial PC, and then
to set it going.  The C-Threads library package, also provided
with MACH, simplifies this.

----

Joe Boykin
Encore Computer Corp
Chairman, IEEE Computer Societies
    Technical Committee on Operating Systems

UUCP: encore!boykin
ARPA: boykin@encore.com