Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!uunet!in1.uu.net!anshar.shadow.net!anshar.shadow.net!nobody
From: dwhite@anshar.shadow.net (Don Whiteside)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Eliminating kernel panics
Date: 16 Jun 1995 11:38:50 -0400
Organization: Shadow Information Services, Inc.
Lines: 27
Message-ID: <3rs8ia$sph@anshar.shadow.net>
References: <3rlecq$i2r@felix.junction.net> <3rnfvm$1qa@park.uvsc.edu>
NNTP-Posting-Host: anshar.shadow.net
X-Newsreader: TIN [version 1.2 PL2]
Terry Lambert (terry@cs.weber.edu) wrote:
[good stuff deleted]
: It's possible to get around most of these problems by not allowing
: the overcommitting of resources; the problem with that is that on
: the the average, it's OK ot overcommit resources, and doing so
: will result in less overall resources being required for the
: average case.
[other good stuff deleted]
Indeed, a signifigant part of an intro Operating Systems course in
computer science is devoted to this subject, and the common consensus
seems to be "this is a management/political issue, not a technical one."
There are multiple schemes to prevent deadlock or avoid it, but they all
involve overhead at a level you'd rather not have overhead. Want to know
that you'll never have a deadlock? Sure we can do that, if your users
don't mind the slowdown and your programmers don't mind these
restrictions:...
=========================================================================
Donald Alan Whiteside MDCC Wage Slave School of Computer Science
Official Usenet Dork for the week of Jan 9-13, 1995
GCS d-- -p+(---) l u+(-) e+ m+ s !n h f g+ w+ t+(++) r- y++
"There's nothing wrong with you I can't fix with my hands..." FM's Batman
=========================================================================