Return to BSD News archive
Newsgroups: comp.os.386bsd.development
Path: sserve!newshost.anu.edu.au!munnari.oz.au!goanna.cs.rmit.oz.au!aggedor.rmit.EDU.AU!harbinger.cc.monash.edu.au!msuinfo!uwm.edu!news.moneng.mei.com!howland.reston.ans.net!usenet.ins.cwru.edu!nigel.msen.com!math.fu-berlin.de!news.th-darmstadt.de!zib-berlin.de!easix!flyer.GUN.de!flatlin!bad
From: bad@flatlin.ka.sub.org (Christoph Badura)
Subject: Re: Notes on the *new* FreeBSD V1.1 VM system
Date: Sat, 26 Feb 1994 22:58:02 GMT
Message-ID: <CLut4r.4DE@flatlin.ka.sub.org>
References: <BcxpGux.dysonj@delphi.com> <2ke3ss$l0d@u.cc.utah.edu> <Ja4p+zR.dysonj@delphi.com> <2kfcur$dd1@germany.eu.net> <2kgdcd$mls@usenet.pa.dec.com>
Organization: Guru Systems/Funware Department
Lines: 18
In <2kgdcd$mls@usenet.pa.dec.com> paik@mlo.dec.com (Samuel S. Paik) writes:
>Please go read the deadlock literature. There are basically four "solution
>strategies" to deadlock: prevention by allowing resources to be allocated
>only in certain patterns; avoidance by refusing to allocate resources when
>you may end up with a deadlock; detection when it occurs and killing to
>break the deadlock; and stick head in the mud (unix).
^^^^mach
This behavior has been introduced only recently (to my knowledge
anyway) in Unix most notably by the Mach VM code and the AIX VM.
Earlier versions of Unix got this right.
--
Christoph Badura bad@flatlin.ka.sub.org +49 721 606137
Es genuegt nicht, keine Gedanken zu haben;
man muss auch unfaehig sein, sie auszudruecken. - Karl Kraus