Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!blackbush.xlink.net!zib-berlin.de!news.tu-chemnitz.de!irz401!uriah.heep!news From: j@uriah.heep.sax.de (J Wunsch) Newsgroups: comp.unix.bsd.freebsd.misc,comp.unix.advocacy Subject: Re: Win32 CreateThread() vs Unix fork() Date: 19 Dec 1995 22:20:57 GMT Organization: Private BSD site, Dresden Lines: 18 Message-ID: <4b7ds9$6bu@uriah.heep.sax.de> References: <4ab85f$idq@news.voicenet.com> <DJBt1u.GFD@tigger.jvnc.net> <4akmsb$qa3@shellx.best.com> <4al3miINNmqt@gambier.ugrad.cs.ubc.ca> <4andei$hmc@bcrkh13.bnr.ca> Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) NNTP-Posting-Host: localhost.heep.sax.de Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: knews 0.9.3 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:10861 comp.unix.advocacy:12409 Will Packard <will@nt.com> writes: > The lack of overhead associated with a thread is the reason to use threads > instead of separate processes. I don't think so. I rather think it's the ability of using a shared data region between all threads, so for the typical example of windowing systems, you could continue to draw an image in one thread while already waiting for new events in the other one. This is rather hard to accomplish with distinct processes (but not impossible, e.g. by extended usage of shared memory between the processes). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)